fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases Wiki Activity
Files
c082d72bdcf7b2a54e262fdafbe084cd2ac63a62
Sylpheed/tools/ppc-manual/control/mtfsb1x.md
sim 7f8a81b8f8
All checks were successful
CI / Native — linux (pull_request) Successful in 2h2m37s
Details
CI / WASM — Web (pull_request) Successful in 30m13s
Details
CI / Formatting (pull_request) Successful in 1m23s
Details
docs(ppc-manual): quote Canary and our own decoder, not the retired xenia-rs 
The generator had not been able to run correctly since the manual moved into
`tools/ppc-manual/`: it computed the repository root as `HERE.parent.parent`,
which now names `tools/`, so the XML, Canary's emitters and xenia-rs all stopped
resolving — silently, because both scrapers skipped what they could not find.
Every page's references had been pointing at paths that exist nowhere.

What each source contributed, measured on the 350 pages before this change:

  Operation (pseudocode)  251 pages: fixed boilerplate "derives from the xenia-rs
                          interpreter"; 99 carry real hand-written seeds
  C translation           337 pages: the same kind of boilerplate
  xenia-rs snapshot       336 pages: the interpreter arm, pasted in — the only
                          per-instruction semantics on unseeded pages
  links                   xenia-rs opcode/decoder/interpreter + Canary emitter

Now:

  * semantics come from **Xenia Canary**, the reference emulator, read through
    `git show` at a pinned upstream commit (`origin/canary_experimental`,
    f21ebd49e9). Not our checkout: it carries instrumentation and lacked
    upstream's `mcrf` fix, so it would have published probes and a wrong `mcrf`.
    Each page embeds the emitter (`InstrEmit_<mnem>`), and for the 128 pure
    one-line delegations also the helper that holds the semantics.
  * decode references point at `crates/sylpheed-ppc` — the decoder that
    produces `sylpheed.db` — as in-repo relative links.
  * the boilerplate now says what is true, and the C translation guide maps
    Canary's actual HIR calls, checked against `ppc_hir_builder.h` (including
    that `UpdateCR(n, v)` truncates to 32 bits).
  * `rust_scraper.py` -> `decoder_scraper.py` (interpreter half dropped);
    missing sources are now errors, not empty results.

Verified:

  consistency checks        455 XML entries, 350 families, 598 index keys
  hand-written tails        386/386 byte-identical after regeneration
  xenia-rs in generated     0
  pages with a snapshot     349/350 (was 336) — `dcbi` has no Canary emitter at all
  in-repo decoder links     910/910 resolve to a line holding the identifier
  emitter boundaries        brace counter == column-0 `}` rule on 521/521;
                            preprocessor model unit-tested (#if 0/#else/#elif)
  idempotency               re-run: 0 pages updated, 0 working-tree changes

Hand-written notes (outside the generated regions) are not rewritten here:

  * 110 links into `../../xenia-rs/...` were dead; they now point at the file in
    the archived repository (git.mc02.dev/fabi/xenia-rs @ 8401d4d). Line anchors
    were dropped because the notes predate that commit — 0 of 441 old line
    ranges match it — and a precise-looking wrong anchor is worse than none. The
    link text, which carries the author's line numbers, is unchanged.
  * 140 prose claims about xenia-rs's behaviour remain. 23 are verified to hold
    for Canary too (the 32-bit CR0 truncation, OE left unimplemented); the other
    114 need checking one by one, and some invert — e.g. `divdx` notes a correct
    64-bit CR0 update in xenia-rs where Canary's `UpdateCR` truncates. Left for
    a deliberate pass rather than a blind substitution.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-16 20:34:34 +02:00

5.3 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 0–5): 63
  • Extended opcode: 38
  • 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
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)

; 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

mtfsb1x

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

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.

Related Instructions

  • 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

Reference in New Issue View Git Blame Copy Permalink