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

stfiwx — Store Floating-Point as Integer Word Indexed

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

Assembler Mnemonics

Mnemonic XML entry Flags Description
stfiwx stfiwx Store Floating-Point as Integer Word Indexed

Syntax

stfiwx [FS], [RA0], [RB]

Encoding

stfiwx — form X

  • Opcode word: 0x7c0007ae
  • Primary opcode (bits 05): 31
  • Extended opcode: 983
  • 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
FS stfiwx: read Source floating-point register.
RA0 stfiwx: read Source GPR; when the encoded register number is 0 the operand is the literal 64-bit zero, not r0.
RB stfiwx: read Source GPR.

Register Effects

stfiwx

  • Reads (always): FS, RA0, RB
  • 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

stfiwx

Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_stfiwx(PPCHIRBuilder& f, const InstrData& i) {
  // if RA = 0 then
  //   b <- 0
  // else
  //   b <- (RA)
  // EA <- b + (RB)
  // MEM(EA, 4) <- (FRS)[32:63]
  Value* ea = CalculateEA_0(f, i.X.RA, i.X.RB);
  f.Store(ea, f.ByteSwap(f.Truncate(f.Cast(f.LoadFPR(i.X.RT), INT64_TYPE),
                                    INT32_TYPE)));
  return 0;
}

Special Cases & Edge Conditions

  • Stores low 32 bits of FPR as raw bytes. Writes FRS[32:63] (the low half of the 64-bit FPR bit pattern) verbatim — no IEEE rounding, no float→int conversion. Used in conjunction with fctiw / fctiwz (convert float to integer word, leaving the 32-bit integer in the low half of an FPR) to materialise an integer in memory without going through a GPR.
  • The asymmetric oddity of the FP load/store family. There is no matching "load FP as integer word" — a 32-bit integer is brought in via lwz to a GPR, then to FPR via the memory-round-trip pattern (stw then lfd). stfiwx only exists in the store direction.
  • X-form only — no D-form, no update form. The instruction has only the indexed form. Compilers usually pair it with addi if a constant offset is needed.
  • RA0 semantics. When RA = 0, base is literal zero; stfiwx FS, 0, RB writes at exact RB.
  • No FPSCR effects. Pure data movement — does not look at the value, does not round.
  • Big-endian word write. The 32 bits are written most-significant-byte first into bytes EA..EA+3. Canary reinterprets the FPR as a 64-bit integer, truncates it to the low word and byte-swaps it before the host store.
  • Alignment. Xenon tolerates unaligned 4-byte writes; cache-inhibited storage may raise alignment exceptions on real hardware.
  • MSR[FP] required. Disabled FP unit raises Floating-Point Unavailable.
  • stfd, stfs — regular FP stores.
  • lfd, lfs — FP loads (no lfiwx analog).
  • stw, stwx — integer word stores from a GPR (the GPR-side equivalent).

IBM Reference