Files
Sylpheed/tools/ppc-manual/memory/lswi.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.5 KiB
Raw Blame History

lswi — Load String Word Immediate

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

Assembler Mnemonics

Mnemonic XML entry Flags Description
lswi lswi Load String Word Immediate

Syntax

(no disassembly template)

Encoding

lswi — form X

  • Opcode word: 0x7c0004aa
  • Primary opcode (bits 05): 31
  • Extended opcode: 597
  • 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

lswi

  • 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

lswi

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

Special Cases & Edge Conditions

  • Byte-granular bulk load. Reads NB bytes starting at EA and packs them, big-endian, into successive GPRs starting at RT. Each filled GPR holds 4 bytes in its low word; partial last words are left- (most-significant-byte-) aligned with trailing zero bytes. The byte count NB is held in the RB field of the instruction encoding (1..31), with the special case NB = 0 meaning "32 bytes".
  • Register wraparound at r31 → r0. If the byte count is large enough to spill past r31, the next register is r0, then r1, etc. AIX docs flag the "RA in destination range" and "RB in destination range" cases as invalid. ⚠️ Canary does not implement lswi: its emitter is XEINSTRNOTIMPLEMENTED, so translating one logs "Unimplemented instr" and, with the default break_on_unimplemented_instructions, breaks.
  • RA0 semantics. RA = 0 selects literal zero. There is no RA post-write — lswi is not an update form.
  • Big-endian byte ordering inside each word. First byte read goes into bits 07 of the destination GPR (most-significant byte). There is no Canary behaviour to compare: it does not implement lswi.
  • Last partial word. When NB is not a multiple of 4, the final GPR's unused low bytes are zero. The high bits remain whatever the load placed there.
  • Alignment. The architecture allows arbitrary alignment, but real implementations may take alignment exceptions on cache-inhibited storage. Canary does not implement lswi (XEINSTRNOTIMPLEMENTED), so there is no Canary behaviour to compare.
  • Vanishingly rare in compiled code. Compilers don't emit lswi. Hand-written memcpy cores from the PowerPC SDK era used it for short copies; otherwise it appears mostly in byte-string init helpers.
  • lswx — register-supplied byte-count variant.
  • stswi, stswx — symmetric stores.
  • lmw — word-granular bulk load (multiple of 4 bytes only, no register wrap).
  • lwz, lbz — scalar loads that compilers emit instead.

IBM Reference