Files
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

mffsx — Move from FPSCR

Category: Control / CR / SPR · Form: X · Opcode: 0xfc00048e

Assembler Mnemonics

Mnemonic XML entry Flags Description
mffs mffsx Move from FPSCR
mffs. mffsx Rc=1 Move from FPSCR

Syntax

mffs[Rc] [RD]

Encoding

mffsx — form X

  • Opcode word: 0xfc00048e
  • Primary opcode (bits 05): 63
  • Extended opcode: 583
  • 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
FPSCR mffsx: read Floating-Point Status and Control Register.
FD mffsx: write Destination floating-point register.
CR mffsx: write (conditional) Condition-register update. When Rc=1, CR field 0 (or CR6 for vector compares, CR1 for FPU) is updated from the result.

Register Effects

mffsx

  • Reads (always): FPSCR
  • Reads (conditional): none
  • Writes (always): FD
  • Writes (conditional): CR

Status-Register Effects

  • mffsx: CR0 ← signed-compare(result, 0) with SO ← XER[SO], when Rc=1.

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

mffsx

Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_mffsx(PPCHIRBuilder& f, const InstrData& i) {
  Value* v = f.Cast(f.ZeroExtend(f.LoadFPSCR(), INT64_TYPE), FLOAT64_TYPE);
  f.StoreFPR(i.X.RT, v);
  if (i.X.Rc) {
    f.CopyFPSCRToCR1();
  }
  return 0;
}

Special Cases & Edge Conditions

  • Operation. Reads the 32-bit FPSCR and places it in the low 32 bits of FRT. The high 32 bits of the destination FPR are architecturally undefined; Canary zero-extends the FPSCR to 64 bits and reinterprets that as the FPR's bit pattern, so the high bits are zero. PowerISA explicitly permits implementations to leave anything there.
  • Destination is an FPR, not a GPR. Use stfd to spill the FPR to memory and reload via a GPR if the value is needed in the integer file.
  • mffs. (Rc=1) updates CR1. The Rc bit copies the high four FPSCR bits (FX, FEX, VX, OX) into CR1's LT/GT/EQ/SO. Canary implements this via CopyFPSCRToCR1.
  • No FPSCR side effect. Pure read; FPSCR is not modified (unlike mcrfs, which clears sticky exception bits).
  • Canary simplification. Canary keeps FPSCR as a 32-bit field but does not maintain the IEEE-754 sticky bits — its UpdateFPSCR is a stub that only clears FEX/VX. So mffs returns what mtfsf/mtfsfi/mcrfs last wrote (initially 0), zero-extended into the FPR's bit pattern. Real titles use it mostly to save/restore the rounding-mode field around library calls, which works: restoring through mtfsf also reloads the host rounding mode.
  • Not synchronising. Reorderable with non-FPU instructions.
  • mtfsfx — write fields of FPSCR from an FPR (the inverse).
  • mtfsb0x, mtfsb1x — set/clear individual FPSCR bits.
  • mtfsfix — load a 4-bit immediate into one FPSCR field.
  • mcrfs — copy an FPSCR field into a CR field (and clear sticky bits).
  • mfspr — for non-FPSCR special registers.

mffs is the simplified mnemonic for the base form (Rc=0); mffs. is the recording variant.

IBM Reference