Files
Sylpheed/tools/ppc-manual/memory/lswx.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

5.2 KiB
Raw Blame History

lswx — Load String Word Indexed

Category: Memory · Form: X · Opcode: 0x7c00042a

Assembler Mnemonics

Mnemonic XML entry Flags Description
lswx lswx Load String Word Indexed

Syntax

(no disassembly template)

Encoding

lswx — form X

  • Opcode word: 0x7c00042a
  • Primary opcode (bits 05): 31
  • Extended opcode: 533
  • Synchronising: no
Bits Field Meaning
05 OPCD primary opcode
610 RT/FRT/VRT destination
1115 RA/FRA/VRA source A
1620 RB/FRB/VRB source B
2130 XO extended opcode (10 bits)
31 Rc record-form flag

Operands

Field Role Description

Register Effects

lswx

  • Reads (always): none
  • Reads (conditional): none
  • Writes (always): none
  • 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

lswx

Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_lswx(PPCHIRBuilder& f, const InstrData& i) {
  XEINSTRNOTIMPLEMENTED();
  return 1;
}

Special Cases & Edge Conditions

  • Byte count from XER[25..31]. Unlike lswi (where the count is encoded as RB), lswx reads XER[25..31] for the byte count NB (0..127). NB = 0 is not the "32 bytes" special case here — zero means literally zero bytes, no registers touched. ⚠️ Canary does not implement lswx: its emitter is XEINSTRNOTIMPLEMENTED, so translating one logs "Unimplemented instr" and, with the default break_on_unimplemented_instructions, breaks.
  • Register packing identical to lswi. Bytes are packed big-endian into successive GPRs starting at RT, four bytes per register, with wraparound r31 → r0. Trailing bytes in the last register are zero-padded on the right.
  • RA0 semantics. RA = 0 selects literal zero. The instruction has no update form — RA is not modified.
  • Invalid forms. AIX flags as invalid: RT collides with RA or RB within the destination range; XER[25..31] and NB byte stream wraps around through both RA and RB. Canary does not implement lswx (XEINSTRNOTIMPLEMENTED).
  • Used for non-multiple-of-4 copies. Together with lswi, gives a way to load a runtime-determined byte count without per-byte loops. Compilers don't emit it; rare hand-written copy primitives may.
  • Alignment. Architecture allows arbitrary alignment; cache-inhibited storage may raise alignment exceptions on real hardware.
  • No FPSCR / CR effects. Pure data movement.
  • lswi — sibling with byte count encoded as RB field (immediate-style).
  • stswx, stswi — symmetric stores.
  • lmw — word-granular bulk load (no byte tail handling).
  • lwz, lbz — scalar loads compilers actually emit.

IBM Reference