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.4 KiB
5.4 KiB
crxor — Condition Register XOR
Category: Control / CR / SPR · Form: XL · Opcode:
0x4c000182
Assembler Mnemonics
| Mnemonic | XML entry | Flags | Description |
|---|---|---|---|
crxor |
crxor |
— | Condition Register XOR |
Syntax
crxor [CRBD], [CRBA], [CRBB]
Encoding
crxor — form XL
- Opcode word:
0x4c000182 - Primary opcode (bits 0–5):
19 - Extended opcode:
193 - Synchronising: no
| Bits | Field | Meaning |
|---|---|---|
| 0–5 | OPCD |
primary opcode (19) |
| 6–10 | BT/BO |
target / branch options |
| 11–15 | BA/BI |
source A / CR bit to test |
| 16–20 | BB |
source B |
| 21–30 | XO |
extended opcode (10 bits) |
| 31 | LK |
link flag |
Operands
| Field | Role | Description |
|---|---|---|
CRBA |
crxor: read | CR source bit A (0–31). |
CRBB |
crxor: read | CR source bit B (0–31). |
CRBD |
crxor: write | CR destination bit (0–31). |
Register Effects
crxor
- Reads (always):
CRBA,CRBB - Reads (conditional): none
- Writes (always):
CRBD - Writes (conditional): none
Status-Register Effects
No condition-register or status-register effects.
Operation (pseudocode)
; No hand-written pseudocode for this instruction yet.
; The authoritative semantics are the Canary emitter snapshot under
; Implementation References; about half of Canary's emitters open
; with the PPC-style definition as a comment (`RD <- (RA) + (RB)`).
; Every side effect is also enumerated in the Register Effects and
; Status-Register Effects tables above.
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
crxor
- Canary XML:
tools/ppc-instructions.xml— search formnem="crxor" - Canary emitter:
src/xenia/cpu/ppc/ppc_emit_control.cc:415 - Sylpheed opcode:
crates/sylpheed-ppc/src/opcode.rs:42 - Sylpheed decoder:
crates/sylpheed-ppc/src/decoder.rs:830
Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_crxor(PPCHIRBuilder& f, const InstrData& i) {
// CR[bt] <- CR[ba] xor CR[bb] bt=bo, ba=bi, bb=bb
Value* ba = f.LoadCRField(i.XL.BI >> 2, i.XL.BI & 3);
Value* bb = f.LoadCRField(i.XL.BB >> 2, i.XL.BB & 3);
Value* bt = f.Xor(ba, bb);
f.StoreCRField(i.XL.BO >> 2, i.XL.BO & 3, bt);
return 0;
}
Special Cases & Edge Conditions
- Operation.
CR[CRBD] ← CR[CRBA] XOR CR[CRBB]. Result is 1 iff the two source bits differ. crclr BTidiom. With identical operands,crxor BT, BT, BTalways yields 0 (any bit XOR'd with itself is 0). This is the canonical PowerPC clear-to-0 for a single CR bit; assemblers recognise the simplified mnemoniccrclr BT. Compilers emit it before variadic-argument calls (PPC ABI usescr1.SOto flag presence of FP arguments).- Bit-level operands. Three independent 5-bit absolute CR-bit indices (0..31).
- Use case. Branch on "A != B"; or, with the
crclridiom, zero a CR bit before fall-through CR computation. - No
Rc/OE. No CR0 / XER side effects. - Not synchronising. Reorderable.
- Canary status. Common enough in real code (typically as
crclr 6for the variadic-FP marker) that translators often special-case thecrclrpattern. Canary'sInstrEmit_crxoremits a host XOR of the two bits.
Related Instructions
creqv— the dual;creqv BT, BT, BTis the standard set-to-1 idiom.crand,crandc,crnand— AND family.cror,crorc,crnor— OR family.mcrf— bulk CR-field copy.bcx,bclrx— typical consumers of synthesised CR bits.
Simplified Mnemonics
| Simplified | Expansion | Effect |
|---|---|---|
crclr BT |
crxor BT, BT, BT |
force CR[BT] ← 0 |