Files
Sylpheed/tools/ppc-manual/control/mtfsb1x.md
MechaCat02 6bdbf89ebc
All checks were successful
CI / Native — linux (pull_request) Successful in 37m56s
CI / WASM — Web (pull_request) Successful in 28m5s
CI / Formatting (pull_request) Successful in 59s
chore(tools): adopt the PPC manual and a canary launcher that works anywhere
CONSOLIDATION.md Phase 6. Both lived untracked in the project root -- on one
disk, backed up by nothing.

  tools/ppc-manual/   393 files, 3.7 MB. 455 instructions, 350 family pages,
                      598 mnemonics resolvable through index.json, plus the
                      generator that produced them.
  tools/run-canary.sh the oracle launcher.

🔴 THE LAUNCHER WAS BROKEN IN TWO WAYS AND IS REWRITTEN, not copied:

  * it pointed at `xenia-rs/sylpheed.iso`, a SYMLINK. Wine cannot resolve one
    and says "path invalid", which reads as a corrupt image rather than a path
    problem -- it has cost a session before. It now points at the real file and
    warns if handed a symlink.
  * it hardcoded one machine's absolute paths, and named `xenia-rs`, which this
    consolidation retires. Now derived from the script's own location, with
    SYLPH_CANARY_BIN / SYLPH_ISO overrides and a check that each exists.

The standing constraints are in its header where someone will read them: one
emulator at a time, Canary runs MUTED, and never judge a crash or a hang from
a Bash-launched run -- a SIGKILL that looked like the binary was the editor's
process supervisor.

⚠️ The manual's GENERATOR reads the xenia-rs source tree, which is going away.
Its decoder now lives here as crates/sylpheed-ppc, so the generator must be
repointed before it is run again. Recorded in the README rather than left for
someone to discover; the manual's content is checked in and regenerates from
nothing implicitly.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-13 21:18:00 +02:00

5.4 KiB
Raw Blame History

mtfsb1x — Move to FPSCR Bit 1

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

Assembler Mnemonics

Mnemonic XML entry Flags Description
mtfsb1 mtfsb1x Move to FPSCR Bit 1
mtfsb1. mtfsb1x Rc=1 Move to FPSCR Bit 1

Syntax

mtfsb1[Rc] [FPSCRD]

Encoding

mtfsb1x — form X

  • Opcode word: 0xfc00004c
  • Primary opcode (bits 05): 63
  • Extended opcode: 38
  • 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 mtfsb1x: write FPSCR destination field.
CR mtfsb1x: 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

mtfsb1x

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

Status-Register Effects

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

Operation (pseudocode)

; Pseudocode derives directly from the xenia-rs interpreter
; arm (see Implementation References). Operation semantics:
;   - Read source operands from the fields listed under Operands.
;   - Apply the arithmetic / logical / memory action described
;     in the Description field above.
;   - Write results to the destination register(s); update any
;     status bits enumerated under Status-Register Effects.
; Consult the IBM AIX reference link under IBM Reference for
; canonical PPC-style pseudocode where xenia's expression is
; terse.

C Translation Example

/* C translation: the xenia-rs interpreter arm below in           */
/* Implementation References is the authoritative semantic        */
/* snapshot. Translate it line-by-line:                            */
/*   - ctx.gpr[N]  -> r[N]       (or f[]/v[] for FPRs/VRs)        */
/*   - mem.read_u*/write_u* -> mem_read_u*_be / mem_write_u*_be   */
/*   - ctx.update_cr_signed(fld, v) -> update_cr_signed(fld, v)   */
/*   - ctx.xer_ca / xer_ov / xer_so -> xer.CA / xer.OV / xer.SO   */
/* The Register Effects and Status-Register Effects tables above  */
/* enumerate every side effect a faithful translation must emit.  */

Implementation References

mtfsb1x

xenia-rs interpreter body (frozen snapshot)
        PpcOpcode::mtfsb1x => {
            // Set FPSCR bit crbd
            let bit = instr.crbd();
            ctx.fpscr |= 1 << (31 - bit);
            if instr.rc_bit() { update_cr1_from_fpscr(ctx); }
            ctx.pc += 4;
        }

Special Cases & Edge Conditions

  • Operation. Sets (writes 1 to) a single named bit of FPSCR. FPSCRD is a 5-bit absolute index (0..31), big-endian (0 = MSB = FX).
  • Mnemonic name. "1" denotes the value written, not bit position. Pair with mtfsb0x for clears.
  • Restricted bits. PowerISA forbids mtfsb1 from setting FEX (bit 1) or VX (bit 2) directly — both are summary bits derived from other state. mtfsb1 can set FX (bit 0), which is itself a sticky summary; this is occasionally used to force a Program interrupt for testing. xenia-rs does not enforce the restriction; setting summary bits will stick until cleared explicitly.
  • Rc=1. mtfsb1. (Rc=1) updates CR1 with the high four FPSCR bits (FX, FEX, VX, OX) after the set.
  • Common use. Force-set a sticky exception bit to test exception-handling code paths. Also seen in floating-point library setup that wants a known FPSCR seed.
  • xenia simplification. Same caveat as mtfsb0: xenia maintains FPSCR but most FP paths don't read it, so the set has limited downstream effect. The bit will read back correctly via mffsx.
  • Not synchronising. Reorderable.
  • mtfsb0x — clear a single FPSCR bit.
  • mtfsfx — write 4-bit FPSCR fields from an FPR.
  • mtfsfix — write 4-bit immediate into a single FPSCR field.
  • mffsx — read FPSCR.
  • mcrfs — FPSCR field → CR field (clears sticky bits).

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

IBM Reference