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
stswx — Store String Word Indexed
Assembler Mnemonics
| Mnemonic | XML entry | Flags | Description |
|---|---|---|---|
stswx |
stswx |
— | Store String Word Indexed |
Syntax
(no disassembly template)
Encoding
stswx — form X
- Opcode word:
0x7c00052a - Primary opcode (bits 0–5):
31 - Extended opcode:
661 - 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
stswx
- 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
stswx
- Canary XML:
tools/ppc-instructions.xml— search formnem="stswx" - Canary emitter:
src/xenia/cpu/ppc/ppc_emit_memory.cc:742 - Sylpheed opcode:
crates/sylpheed-ppc/src/opcode.rs:255 - Sylpheed decoder:
crates/sylpheed-ppc/src/decoder.rs:945
Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_stswx(PPCHIRBuilder& f, const InstrData& i) {
XEINSTRNOTIMPLEMENTED();
return 1;
}
Special Cases & Edge Conditions
- Byte count from
XER[25..31]. Unlikestswi, the byte countNB(0..127) is read fromXER[25..31].NB = 0means literally zero bytes — the instruction becomes a no-op. ⚠️ Canary does not implementstswx: its emitter isXEINSTRNOTIMPLEMENTED, so translating one logs "Unimplemented instr" and, with the defaultbreak_on_unimplemented_instructions, breaks. - Register packing identical to
stswi. Bytes are pulled from successive GPRs, four bytes per register, big-endian within each register, with wraparoundr31 → r0. The final partial register's unused trailing bytes are not written. RA0semantics.RA = 0selects literal zero. The instruction has no update form —RAis not modified.- Invalid forms. AIX flags as invalid the cases where the byte-stream wraps through
RAorRBwhile reading the source registers. Canary does not implementstswx(XEINSTRNOTIMPLEMENTED). - Big-endian byte ordering inside each register. Writes most-significant byte of each source GPR's low word first.
- Used for non-multiple-of-4 copies. Together with
lswx, gives a way to store a runtime-determined byte count without per-byte loops. Compilers don't emit it. - Alignment. Architecture allows arbitrary alignment; cache-inhibited storage may raise alignment exceptions on hardware.
- No CR / FPSCR effects.
Related Instructions
lswx— symmetric load.stswi— sibling with byte count encoded asRBfield (immediate-style).stmw— word-granular bulk store (no byte tail handling).stw,stb— scalar stores.
IBM Reference
- AIX 7.3 —
stswx(Store String Word Indexed) PowerISA v2.07B Book II§ "Load and Store String" for invalid-form rules andXERinteraction.