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.1 KiB
5.1 KiB
stswi — Store String Word Immediate
Assembler Mnemonics
| Mnemonic | XML entry | Flags | Description |
|---|---|---|---|
stswi |
stswi |
— | Store String Word Immediate |
Syntax
(no disassembly template)
Encoding
stswi — form X
- Opcode word:
0x7c0005aa - Primary opcode (bits 0–5):
31 - Extended opcode:
725 - 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 |
|---|
Register Effects
stswi
- 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
stswi
- Canary XML:
tools/ppc-instructions.xml— search formnem="stswi" - Canary emitter:
src/xenia/cpu/ppc/ppc_emit_memory.cc:737 - Sylpheed opcode:
crates/sylpheed-ppc/src/opcode.rs:254 - Sylpheed decoder:
crates/sylpheed-ppc/src/decoder.rs:950
Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_stswi(PPCHIRBuilder& f, const InstrData& i) {
XEINSTRNOTIMPLEMENTED();
return 1;
}
Special Cases & Edge Conditions
- Byte-granular bulk store. Symmetric counterpart of
lswi. Reads the low 32 bits ofRS,RS+1, …, takes the top byte of each (then the next, etc.) and writes successive bytes atEA. The byte countNBis in theRBfield of the encoding (1..31), withNB = 0meaning "32 bytes". - Register wraparound at r31 → r0. After r31 the source becomes r0, then r1, etc. Rare in practice; AIX flags overlapping register / address ranges as invalid. ⚠️ Canary does not implement
stswi: its emitter isXEINSTRNOTIMPLEMENTED, so translating one logs "Unimplemented instr" and, with the defaultbreak_on_unimplemented_instructions, breaks. - Big-endian byte ordering inside each register. Writes the most-significant byte first:
mem.write_u8(ea, (val >> 24) as u8), then bits 16–23, etc. Matches the byte order produced bylswi, so alswi/stswipair round-trips a buffer. - Last partial register. When
NBis not a multiple of 4, the final source register has its trailing low bytes ignored — only the leading bytes that fit in the byte budget are written. RA0semantics.RA = 0selects literal zero.stswiis not an update form;RAis not modified.- Alignment. Architecture allows arbitrary alignment; cache-inhibited storage may raise alignment exceptions on hardware.
- Vanishingly rare in compiled code. Compilers don't emit
stswi. Hand-writtenmemcpycores may.
Related Instructions
lswi— symmetric load.stswx— register-supplied byte-count variant.stmw— word-granular bulk store.stw,stb— scalar stores compilers actually emit.
IBM Reference
- AIX 7.3 —
stswi(Store String Word Immediate) PowerISA v2.07B Book II§ "Load and Store String".