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

stmw — Store Multiple Word

Category: Memory · Form: D · Opcode: 0xbc000000

Assembler Mnemonics

Mnemonic XML entry Flags Description
stmw stmw Store Multiple Word

Syntax

(no disassembly template)

Encoding

stmw — form D

  • Opcode word: 0xbc000000
  • Primary opcode (bits 05): 47
  • Extended opcode:
  • Synchronising: no
Bits Field Meaning
05 OPCD primary opcode
610 RT destination GPR (or RS when storing)
1115 RA source GPR (0 ⇒ literal 0 for RA0 forms)
1631 D/SI/UI 16-bit signed or unsigned immediate

Operands

Field Role Description

Register Effects

stmw

  • 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

stmw

Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_stmw(PPCHIRBuilder& f, const InstrData& i) {
  Value* b;
  if (i.D.RA == 0) {
    b = f.LoadZeroInt64();
  } else {
    b = f.LoadGPR(i.D.RA);
  }

  for (uint32_t j = 0; j < 32 - i.D.RT; ++j) {
    Value* offset = f.LoadConstantInt64(XEEXTS16(i.D.DS) + j * 4);
    f.StoreOffset(b, offset,
                  f.ByteSwap(f.Truncate(f.LoadGPR(i.D.RT + j), INT32_TYPE)));
  }
  return 0;
}

Special Cases & Edge Conditions

  • Bulk register save. Stores (32 - RS) consecutive 32-bit words taken from r[RS], r[RS+1], …, r31 to memory starting at EA. The symmetric counterpart of lmw. Used by AIX/PowerPC ABI prologues to save non-volatile GPRs in one instruction.
  • Each store is the low 32 bits of the GPR. Canary stores ByteSwap(Truncate(GPR, INT32)) for each register — only the low half of the 64-bit GPR. The high 32 bits are discarded; stmw cannot save 64-bit values (use a sequence of std instead).
  • Big-endian write. Word from r[RS] lands at EA, word from r[RS+1] at EA+4, etc. Each word is itself written most-significant-byte first.
  • RA0 semantics. When RA = 0, base is the literal zero. Useful for absolute-address restoration.
  • Alignment. PowerISA requires word-aligned EA; an unaligned stmw may raise an alignment exception on hardware. Canary does not check.
  • Performance trap. Modern PowerPC implementations microcode stmw — typically slower than the same number of stw instructions. Compilers prefer the unrolled form.
  • Cache-line behaviour. When the run of words crosses several 128-byte cache lines, each cold line triggers a read-allocate. Pre-clearing with dcbz128 helps for fresh frames.
  • lmw — symmetric "load multiple words" (the matching epilogue partner).
  • stw, stwx — single-word stores; the modern preferred form.
  • stswi, stswx — store string (byte-granular bulk transfer).
  • std — for 64-bit values (no "store multiple doubleword" exists).

IBM Reference