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>
6.2 KiB
6.2 KiB
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 0–5):
31 - Extended opcode:
138 - Synchronising: no
| Bits | Field | Meaning |
|---|---|---|
| 0–5 | OPCD |
primary opcode (31) |
| 6–10 | RT |
destination GPR |
| 11–15 | RA |
source A |
| 16–20 | RB |
source B |
| 21 | OE |
overflow-enable flag |
| 22–30 | XO |
extended opcode (9 bits) |
| 31 | Rc |
record-form flag |
Operands
| Field | Role | Description |
|---|---|---|
RA |
addex: read | Source GPR (r0–r31). |
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) withSO ← XER[SO], whenRc=1.; XER[OV] ← signed-overflow(result); XER[SO] stickies, whenOE=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 XML:
tools/ppc-instructions.xml— search formnem="addex" - Canary emitter:
src/xenia/cpu/ppc/ppc_emit_alu.cc:83 - Sylpheed opcode:
crates/sylpheed-ppc/src/opcode.rs:9 - Sylpheed decoder:
crates/sylpheed-ppc/src/decoder.rs:983
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.
addexis the middle link of a multi-word add chain seeded byaddcx:RT ← RA + RB + XER[CA], thenXER[CA] ← carry_out. - Carry-out detection handles both edges. Canary's
AddWithCarryDidCarry(after PearPC) setsCAif(a + b) <u aor(a + b + ca) <u ca— the second clause covers the case where adding the carry-in alone wraps (RB == ~0 && CA == 1), which the naiveresult < ratest misses. ⚠️ It works on the low 32 bits ofRA/RB, soCAis the 32-bit carry, not the 64-bit one. - No trap on signed overflow.
addeo/addeo.only updateXER[OV]and stickyXER[SO]. Canary'sOEbranch is an empty stub ("TODO: Handle overflow flag"), soOVis never set — unlikeaddme/addze,CAis still stored. - 64-bit CR update on Xenon, 32-bit in Canary.
f.UpdateCR(0, v)truncatesvtoINT32before 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; seeaddx. XER[CA]must be initialised by an earlieraddcx,subfcx, ormtsprto XER. Reading staleCAfrom an unrelated instruction is the most common bug in hand-written multi-word arithmetic.XER[SO]is sticky until cleared bymcrxr;Rc=1copies it intoCR0[SO].
Related Instructions
addcx— seeds the carry chain (noCAread, setsCA).addmex,addzex— terminate the chain (RA + −1 + CA,RA + 0 + CA).addx— plain add withoutXER[CA].subfex— dual:~RA + RB + XER[CA], used for multi-word subtract.addic/addicx— immediate carrying adds that initialise a chain.
IBM Reference
- AIX 7.3 —
adde(Add Extended) - PowerISA v2.07B, Book I, §3.3.8 — defines the
RA + RB + CAcarry-chain composition.