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>
4.8 KiB
4.8 KiB
fmrx — Floating Move Register
Category: Floating-Point · Form: X · Opcode:
0xfc000090
Assembler Mnemonics
| Mnemonic | XML entry | Flags | Description |
|---|---|---|---|
fmr |
fmrx |
— | Floating Move Register |
fmr. |
fmrx |
Rc=1 | Floating Move Register |
Syntax
fmr[Rc] [FD], [FB]
Encoding
fmrx — form X
- Opcode word:
0xfc000090 - Primary opcode (bits 0–5):
63 - Extended opcode:
72 - 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 |
|---|---|---|
FB |
fmrx: read | Source B floating-point register. |
FD |
fmrx: write | Destination floating-point register. |
CR |
fmrx: 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
fmrx
- Reads (always):
FB - Reads (conditional): none
- Writes (always):
FD - Writes (conditional):
CR
Status-Register Effects
fmrx: CR0 ← signed-compare(result, 0) withSO ← XER[SO], whenRc=1.
Operation (pseudocode)
FRT <- FRB
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
fmrx
- xenia-canary XML:
tools/ppc-instructions.xml— search formnem="fmrx" - xenia-canary emit:
src/xenia/cpu/ppc/ppc_emit_fpu.cc:496 - xenia-rs opcode:
crates/xenia-cpu/src/opcode.rs:28 - xenia-rs decoder:
crates/xenia-cpu/src/decoder.rs:906 - xenia-rs interpreter:
crates/xenia-cpu/src/interpreter.rs:2752-2756
xenia-rs interpreter body (frozen snapshot)
PpcOpcode::fmrx => {
ctx.fpr[instr.rd()] = ctx.fpr[instr.rb()];
if instr.rc_bit() { update_cr1_from_fpscr(ctx); }
ctx.pc += 4;
}
Special Cases & Edge Conditions
- Bit-pattern copy, no rounding.
fmrcopies the 64-bit binary representation ofFRBintoFRTunchanged. No precision loss, no FPSCR exception bits, no NaN quietening. xenia-rs implements this as a plainf64copy. - NaN preserved verbatim. Signalling/quiet bit, payload, and sign are all preserved exactly. Unlike arithmetic instructions,
fmrdoes not quieten signalling NaNs. - Special values. All bit patterns pass through untouched, including ±0, ±∞, and any NaN. The destination receives an exact copy.
- FPSCR. Hardware does not update
FPRFor any exception bit. The "FPSCR write" implied in the header refers only toRc=1updating CR1 from existing FPSCR contents. Rc=1(fmr.) copiesFPSCR[FX, FEX, VX, OX]into CR1.- No
FRA. X-form, primary 63, XO 72. ReadsFRBonly. - Cheaper than load-store. Compilers emit
fmrfor FPR-to-FPR moves; transferring a value via memory (stfd/lfd) would be far more expensive.
Related Instructions
fabsx,fnegx,fnabsx— sign-bit variants of the move (clear / toggle / set).fselx— branch-free select; like a conditionalfmr.mffsx— read FPSCR into an FPR; complementary "FPR move" for a control register.stfd/lfd— memory-mediated FPR transfer (much slower; used for register window spills).
IBM Reference
- AIX 7.3 —
fmr(Floating Move Register) - PowerISA v2.07B, Book I, Chapter 4 — Floating-Point Processor (move-class instructions explicitly bypass quietening and FPSCR side effects).