Files
Sylpheed/tools/ppc-manual/alu/addex.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

6.2 KiB
Raw Permalink Blame History

addex — Add Extended

Category: Integer ALU · Form: XO · Opcode: 0x7c000114

Assembler Mnemonics

Mnemonic XML entry Flags Description
adde addex Add Extended
addeo addex OE=1 Add Extended
adde. addex Rc=1 Add Extended
addeo. addex OE=1, Rc=1 Add Extended

Syntax

adde[OE][Rc] [RD], [RA], [RB]

Encoding

addex — form XO

  • Opcode word: 0x7c000114
  • Primary opcode (bits 05): 31
  • Extended opcode: 138
  • Synchronising: no
Bits Field Meaning
05 OPCD primary opcode (31)
610 RT destination GPR
1115 RA source A
1620 RB source B
21 OE overflow-enable flag
2230 XO extended opcode (9 bits)
31 Rc record-form flag

Operands

Field Role Description
RA addex: read Source GPR (r0r31).
RB addex: read Source GPR.
CA addex: read XER[CA] carry bit. Read by add-with-carry/subtract-with-borrow instructions, written by carrying instructions.
RD addex: write Destination GPR.
OE addex: write (conditional) Overflow-enable bit. When 1, the instruction updates XER[OV] and stickies XER[SO] on signed overflow.
CR addex: 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

addex

  • Reads (always): RA, RB, CA
  • Reads (conditional): none
  • Writes (always): RD
  • Writes (conditional): OE, CR

Status-Register Effects

  • addex: CR0 ← signed-compare(result, 0) with SO ← XER[SO], when Rc=1.; XER[OV] ← signed-overflow(result); XER[SO] stickies, when OE=1.

Operation (pseudocode)

RT <- (RA) + (RB) + CA
CA <- carry_out_of_the_add

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

addex

Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_addex(PPCHIRBuilder& f, const InstrData& i) {
  // RD <- (RA) + (RB) + XER[CA]
  // CA <- carry bit
  Value* ra = f.LoadGPR(i.XO.RA);
  Value* rb = f.LoadGPR(i.XO.RB);
  Value* v = f.AddWithCarry(ra, rb, f.LoadCA());
  f.StoreGPR(i.XO.RT, v);
  f.StoreCA(AddWithCarryDidCarry(f, ra, rb, f.LoadCA()));
  if (i.XO.Rc) {
    f.UpdateCR(0, v);
  }
  if (i.XO.OE) {
    // Stub implementation.
    // TODO: Handle overflow flag.
    // NOTE: 535507D4 (Raiden Fighters Aces) never seems to rely on this
    //   behavior either, despite OE being set.
  }
  return 0;
}

Special Cases & Edge Conditions

  • Carry-in is consumed and carry-out is produced. addex is the middle link of a multi-word add chain seeded by addcx: RT ← RA + RB + XER[CA], then XER[CA] ← carry_out.
  • Carry-out detection handles both edges. Canary's AddWithCarryDidCarry (after PearPC) sets CA if (a + b) <u a or (a + b + ca) <u ca — the second clause covers the case where adding the carry-in alone wraps (RB == ~0 && CA == 1), which the naive result < ra test misses. ⚠️ It works on the low 32 bits of RA/RB, so CA is the 32-bit carry, not the 64-bit one.
  • No trap on signed overflow. addeo/addeo. only update XER[OV] and sticky XER[SO]. Canary's OE branch is an empty stub ("TODO: Handle overflow flag"), so OV is never set — unlike addme/addze, CA is still stored.
  • 64-bit CR update on Xenon, 32-bit in Canary. f.UpdateCR(0, v) truncates v to INT32 before the signed compare with zero. For multi-word adds whose final word is the high 32 bits of a 64-bit value, this distinction matters; see addx.
  • XER[CA] must be initialised by an earlier addcx, subfcx, or mtspr to XER. Reading stale CA from an unrelated instruction is the most common bug in hand-written multi-word arithmetic.
  • XER[SO] is sticky until cleared by mcrxr; Rc=1 copies it into CR0[SO].
  • addcx — seeds the carry chain (no CA read, sets CA).
  • addmex, addzex — terminate the chain (RA + 1 + CA, RA + 0 + CA).
  • addx — plain add without XER[CA].
  • subfex — dual: ~RA + RB + XER[CA], used for multi-word subtract.
  • addic / addicx — immediate carrying adds that initialise a chain.

IBM Reference