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>
5.6 KiB
5.6 KiB
addzex — Add to Zero Extended
Category: Integer ALU · Form: XO · Opcode:
0x7c000194
Assembler Mnemonics
| Mnemonic | XML entry | Flags | Description |
|---|---|---|---|
addze |
addzex |
— | Add to Zero Extended |
addzeo |
addzex |
OE=1 | Add to Zero Extended |
addze. |
addzex |
Rc=1 | Add to Zero Extended |
addzeo. |
addzex |
OE=1, Rc=1 | Add to Zero Extended |
Syntax
addze[OE][Rc] [RD], [RA]
Encoding
addzex — form XO
- Opcode word:
0x7c000194 - Primary opcode (bits 0–5):
31 - Extended opcode:
202 - 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 |
addzex: read | Source GPR (r0–r31). |
CA |
addzex: read; addzex: write | XER[CA] carry bit. Read by add-with-carry/subtract-with-borrow instructions, written by carrying instructions. |
RD |
addzex: write | Destination GPR. |
OE |
addzex: write (conditional) | Overflow-enable bit. When 1, the instruction updates XER[OV] and stickies XER[SO] on signed overflow. |
CR |
addzex: 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
addzex
- Reads (always):
RA,CA - Reads (conditional): none
- Writes (always):
RD,CA - Writes (conditional):
OE,CR
Status-Register Effects
addzex: CR0 ← signed-compare(result, 0) withSO ← XER[SO], whenRc=1.; XER[OV] ← signed-overflow(result); XER[SO] stickies, whenOE=1.; XER[CA] ← carry-out of the add / borrow-in of the subtract (always).
Operation (pseudocode)
RT <- (RA) + CA
CA <- carry_out
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
addzex
- Canary XML:
tools/ppc-instructions.xml— search formnem="addzex" - Canary emitter:
src/xenia/cpu/ppc/ppc_emit_alu.cc:172 - Sylpheed opcode:
crates/sylpheed-ppc/src/opcode.rs:16 - Sylpheed decoder:
crates/sylpheed-ppc/src/decoder.rs:985
Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_addzex(PPCHIRBuilder& f, const InstrData& i) {
// RT <- (RA) + CA
// CA <- carry bit
Value* ra = f.LoadGPR(i.XO.RA);
Value* v = f.AddWithCarry(ra, f.LoadZeroInt64(), f.LoadCA());
f.StoreGPR(i.XO.RT, v);
if (i.XO.OE) {
// With XER[SO] update too.
// e.update_xer_with_overflow_and_carry(b.CreateExtractValue(v, 1));
XEINSTRNOTIMPLEMENTED();
} else {
// Just CA update.
f.StoreCA(AddWithCarryDidCarry(f, ra, f.LoadZeroInt64(), f.LoadCA()));
}
if (i.XO.Rc) {
f.UpdateCR(0, v);
}
return 0;
}
Special Cases & Edge Conditions
- No
RBfield used. Likeaddmex, this XO-form instruction ignores theRBslot. Assemblers emit zero there. - Operation is
RA + 0 + CA≡RA + CA. Used to terminate the high word of a multi-word add chain seeded byaddcx. After the low-wordaddcproduces the carry, all middle words useaddex, and the final word that has no register operand usesaddze. - Carry-out is the simple unsigned overflow test
result < ra— same predicate asaddcx.CA' = 1only ifRA == ~0 && CA == 1. OE=1not implemented in Canary. The branch isXEINSTRNOTIMPLEMENTED()and does not storeCA; spec asks for the standard signed-overflow detect.- 64-bit CR update on Xenon, 32-bit in Canary (
f.UpdateCR(0, v)— seeaddxfor context). - Common idiom: extracting a carry as a 0/1.
addze rT, 0(oraddze rT, rNwhererN == 0) materialisesXER[CA]intorTas a plain integer.
Related Instructions
addmex— terminate withRA + (−1) + CAinstead of+0.addex— middle of a multi-word add chain.addcx— seeds the chain.subfzex— subtract dual:~RA + 0 + CA.