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

mtfsb0x — Move to FPSCR Bit 0

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

Assembler Mnemonics

Mnemonic XML entry Flags Description
mtfsb0 mtfsb0x Move to FPSCR Bit 0
mtfsb0. mtfsb0x Rc=1 Move to FPSCR Bit 0

Syntax

mtfsb0[Rc] [FPSCRD]

Encoding

mtfsb0x — form X

  • Opcode word: 0xfc00008c
  • Primary opcode (bits 05): 63
  • Extended opcode: 70
  • 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
FPSCRD mtfsb0x: write FPSCR destination field.
CR mtfsb0x: 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

mtfsb0x

  • Reads (always): none
  • Reads (conditional): none
  • Writes (always): FPSCRD
  • Writes (conditional): CR

Status-Register Effects

  • mtfsb0x: 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

mtfsb0x

Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_mtfsb0x(PPCHIRBuilder& f, const InstrData& i) {
  XEINSTRNOTIMPLEMENTED();
  return 1;
}

Special Cases & Edge Conditions

  • Operation. Clears (sets to 0) a single named bit of the 32-bit FPSCR. The bit is selected by FPSCRD (a 5-bit absolute index 0..31, big-endian: 0 = MSB = FX).
  • The mnemonic name "Bit 0" is misleading. "0" refers to the value being written, not to bit position 0. Pair with mtfsb1x which writes a 1.
  • Restricted bits. Per PowerISA, mtfsb0 cannot clear bits 1 (FEX) or 2 (VX) — those are summary bits, derived from other FPSCR bits. ⚠️ Canary does not implement mtfsb0: its emitter is XEINSTRNOTIMPLEMENTED, so translating one logs "Unimplemented instr" and, with the default break_on_unimplemented_instructions, breaks.
  • Rc=1. mtfsb0. (Rc=1) updates CR1 with the high four FPSCR bits (FX, FEX, VX, OX) after the clear. This is the FPU's record-form analogue.
  • Common use. Reset a sticky exception bit ahead of a sequence of FP ops you want to monitor (e.g. mtfsb0 5 to clear ZX before a divide series, then read it back).
  • Canary status. With mtfsb0 unimplemented, Canary never clears the bit (and breaks by default, see above). Most FP instructions in Canary do not update FPSCR exception bits either, so titles that manage rounding only through mtfsf/mtfsfi are unaffected.
  • Not synchronising. Reorderable.
  • mtfsb1x — set a single FPSCR bit to 1.
  • mtfsfx — write fields of FPSCR from an FPR.
  • mtfsfix — write a 4-bit immediate into one FPSCR field.
  • mffsx — read FPSCR.
  • mcrfs — copy FPSCR field → CR field (and clear sticky bits).

mtfsb0 is itself the simplified form (Rc=0); mtfsb0. is the recording variant.

IBM Reference