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.7 KiB
5.7 KiB
ldbrx — Load Doubleword Byte-Reverse Indexed
Assembler Mnemonics
| Mnemonic | XML entry | Flags | Description |
|---|---|---|---|
ldbrx |
ldbrx |
— | Load Doubleword Byte-Reverse Indexed |
Syntax
ldbrx [RD], [RA0], [RB]
Encoding
ldbrx — form X
- Opcode word:
0x7c000428 - Primary opcode (bits 0–5):
31 - Extended opcode:
532 - Synchronising: no
| Bits | Field | Meaning |
|---|---|---|
| 0–5 | OPCD |
primary opcode |
| 6–10 | RT/FRT/VRT |
destination |
| 11–15 | RA/FRA/VRA |
source A |
| 16–20 | RB/FRB/VRB |
source B |
| 21–30 | XO |
extended opcode (10 bits) |
| 31 | Rc |
record-form flag |
Operands
| Field | Role | Description |
|---|---|---|
RA0 |
ldbrx: read | Source GPR; when the encoded register number is 0 the operand is the literal 64-bit zero, not r0. |
RB |
ldbrx: read | Source GPR. |
RD |
ldbrx: write | Destination GPR. |
Register Effects
ldbrx
- Reads (always):
RA0,RB - Reads (conditional): none
- Writes (always):
RD - 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
ldbrx
- Canary XML:
tools/ppc-instructions.xml— search formnem="ldbrx" - Canary emitter:
src/xenia/cpu/ppc/ppc_emit_memory.cc:654 - Sylpheed opcode:
crates/sylpheed-ppc/src/opcode.rs:108 - Sylpheed decoder:
crates/sylpheed-ppc/src/decoder.rs:931
Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_ldbrx(PPCHIRBuilder& f, const InstrData& i) {
// if RA = 0 then
// b <- 0
// else
// b <- (RA)
// EA <- b + (RB)
// RT <- bswap(MEM(EA, 8))
Value* ea = CalculateEA_0(f, i.X.RA, i.X.RB);
Value* rt = f.Load(ea, INT64_TYPE);
f.StoreGPR(i.X.RT, rt);
return 0;
}
Special Cases & Edge Conditions
- Reads little-endian.
ldbrxloads 8 bytes and reverses byte order before placing them inRT. With Xenon's PowerPC big-endian world view, the architectural effect is "load a little-endian doubleword as if it were big-endian" — useful when consuming network buffers, file headers (PNG IHDR, ZIP CRC32, etc.), or PC-side data structures that store little-endian. - Implementation detail. Canary loads the doubleword without the byte swap
ldapplies, which on its little-endian host gives the little-endian interpretation directly. Equivalent to four sequentiallbzplus shifts, but issued as one micro-op. - No update form, X-form only. PowerPC byte-reverse loads come in indexed form only (no
ldbrxuor DS-form).EA = (RA|0) + RB. To increment a pointer, fold the increment intoRBor use a separateaddi. RA0semantics. WhenRA = 0, base is the literal zero;ldbrx RT, 0, RBreads at exactRB.- Alignment. Like the rest of the byte-reverse family,
ldbrxdoes not require natural alignment on hardware; the load is done as eight byte reads internally. Xenon may take an alignment exception on cache-inhibited storage. - No corresponding sign-extension. The output is the literal byte-reversed bit pattern; it occupies the full 64-bit register. Use shifts or
extsw/extshafterwards if a sign-extended narrower datum is desired. - Pair with
stdbrx. The store side performs the inverse: takes the GPR value, reverses, writes 8 bytes.
Related Instructions
stdbrx— store doubleword byte-reverse indexed.lwbrx,lhbrx— narrower byte-reverse loads (word, halfword).stwbrx,sthbrx— narrower byte-reverse stores.ld,ldx— non-reversing doubleword loads.
IBM Reference
- AIX 7.3 —
ldbrx(Load Doubleword Byte-Reverse Indexed) PowerISA v2.07B Book II§ "Byte-Reverse Storage Access".