Files
Sylpheed/tools/ppc-manual/alu/andcx.md
sim f3c512f2ab docs(ppc-manual): check every xenia-rs claim against Canary's source
The hand-written parts of the manual still described how the retired
xenia-rs interpreter behaved: its snapshots, Rust casts and helpers. Each of
those 490 statements is now either restated as what Canary's emitters and
x64 backend actually do (at the pinned canary_experimental commit), or
dropped where it only made sense for xenia-rs.

Checking them turned up claims that were wrong, not just outdated:

- VSCR[SAT] is never modelled in Canary (DID_SATURATE is a stub and mfvscr
  cannot see it); the pages said saturating ops set it stickily.
- Canary does not implement lswi/lswx/stswi/stswx, dcbi, mtfsb0/mtfsb1,
  vmsum*, vmhaddshs, vupkhpx/vupklpx, and most SPRs; pages described them
  as working.
- Traps evaluate TO in Canary; stvebx/stvehx/stvewx store one element, not
  16 bytes; mtmsrd writes only EE; fres/frsqrte/vrsqrtefp precision claims
  and the stfs "rounds under RN / sets FPSCR" claim contradicted the spec.
- Reservations are a 64 KiB block bitmap plus a value compare, not
  per-address tracking.

Claims that neither Canary's source nor a public spec settles are marked
unverified (NI at boot, vmaddcfp128 operand order, estimate bit-exactness).

Generated regions are untouched; re-running the generator changes nothing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-16 21:52:38 +02:00

4.6 KiB
Raw Permalink Blame History

andcx — AND with Complement

Category: Integer ALU · Form: X · Opcode: 0x7c000078

Assembler Mnemonics

Mnemonic XML entry Flags Description
andc andcx AND with Complement
andc. andcx Rc=1 AND with Complement

Syntax

andc[Rc] [RA], [RS], [RB]

Encoding

andcx — form X

  • Opcode word: 0x7c000078
  • Primary opcode (bits 05): 31
  • Extended opcode: 60
  • Synchronising: no
Bits Field Meaning
05 OPCD primary opcode
610 RT/FRT/VRT destination
1115 RA/FRA/VRA source A
1620 RB/FRB/VRB source B
2130 XO extended opcode (10 bits)
31 Rc record-form flag

Operands

Field Role Description
RS andcx: read Source GPR (alias for RD in some stores).
RB andcx: read Source GPR.
RA andcx: write Source GPR (r0r31).
CR andcx: write (conditional) Condition-register update. When Rc=1, CR field 0 (or CR6 for vector compares, CR1 for FPU) is updated from the result.

Register Effects

andcx

  • Reads (always): RS, RB
  • Reads (conditional): none
  • Writes (always): RA
  • Writes (conditional): CR

Status-Register Effects

  • andcx: CR0 ← signed-compare(result, 0) with SO ← XER[SO], when Rc=1.

Operation (pseudocode)

RA <- (RS) & ~(RB)

C Translation Example

/* No hand-written C yet. Translate the Canary emitter snapshot   */
/* under Implementation References; its HIR maps directly:        */
/*   f.LoadGPR(n) / f.StoreGPR(n, v)  -> r[n] / r[n] = v          */
/*   f.LoadFPR / StoreFPR, f.LoadVR / StoreVR -> f[n], v[n]        */
/*   f.Load(ea, T), f.Store(ea, v) -> raw read / write; emitters   */
/*     wrap them in f.ByteSwap for the big-endian guest value      */
/*   f.UpdateCR(n, v)  -> CR field n from v's LOW 32 BITS vs 0     */
/*   f.LoadCA / f.StoreCA -> xer.CA;  f.StoreSAT -> vscr.SAT       */
/*   i.XO.RA, i.D.DS, ... -> the bit-fields listed under Operands  */
/* The Register Effects and Status-Register Effects tables above  */
/* enumerate every side effect a faithful translation must emit.  */

Implementation References

andcx

Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_andcx(PPCHIRBuilder& f, const InstrData& i) {
  // RA <- (RS) & ¬(RB)
  Value* ra = f.AndNot(f.LoadGPR(i.X.RT), f.LoadGPR(i.X.RB));
  f.StoreGPR(i.X.RA, ra);
  if (i.X.Rc) {
    f.UpdateCR(0, ra);
  }
  return 0;
}

Special Cases & Edge Conditions

  • andc RA, RS, RB computes RS AND (NOT RB). The complement is applied to RB, not RS. Useful for clearing a bitmask: andc r3, r3, r4 clears in r3 every bit set in r4.
  • Common idiom: andc r3, r3, r3 zeroes r3 (every bit ANDed with its own complement). Cheaper-looking than xor r3, r3, r3 on some pipelines but functionally identical; the assembler often prefers the xor idiom.
  • Operand convention is the X-form one (RA is the destination, RS and RB are sources). Same gotcha as andx.
  • No OE/XER side effects. Only CR0 is updated when Rc=1.
  • 64-bit operation on Xenon; the AND is computed across all 64 bits of RS and ~RB. Canary emits a single full-width f.AndNot(RS, RB).
  • 64-bit CR update on Xenon, 32-bit in Canaryf.UpdateCR(0, ra), the same INT32 truncation.
  • andx — plain AND (no complement).
  • nandx — NAND (~(RS & RB)).
  • orcx — OR with complement; sister c form.
  • eqvx~(RS ^ RB) (NXOR / equivalence).
  • norx — NOR.

IBM Reference