Files
Sylpheed/tools/ppc-manual/fpu/fcmpo.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

6.7 KiB
Raw Blame History

fcmpo — Floating Compare Ordered

Category: Floating-Point · Form: X · Opcode: 0xfc000040

Assembler Mnemonics

Mnemonic XML entry Flags Description
fcmpo fcmpo Floating Compare Ordered

Syntax

fcmpo [CRFD], [FA], [FB]

Encoding

fcmpo — form X

  • Opcode word: 0xfc000040
  • Primary opcode (bits 05): 63
  • Extended opcode: 32
  • 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
FA fcmpo: read Source A floating-point register (fr0fr31).
FB fcmpo: read Source B floating-point register.
CRFD fcmpo: write CR destination field (crf, 07).
FPSCR fcmpo: write Floating-Point Status and Control Register.

Register Effects

fcmpo

  • Reads (always): FA, FB
  • Reads (conditional): none
  • Writes (always): CRFD, FPSCR
  • Writes (conditional): none

Status-Register Effects

  • fcmpo: FPSCR updated per IEEE-754 flags (FX, FEX, FPRF, FR, FI, exceptions).

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

fcmpo

xenia-rs interpreter body (frozen snapshot)
        PpcOpcode::fcmpo => {
            // Ordered compare: like fcmpu but also sets VXVC on QNaN (or VXSNAN on SNaN).
            let fra = ctx.fpr[instr.ra()];
            let frb = ctx.fpr[instr.rb()];
            let crfd = instr.crfd();
            if fra.is_nan() || frb.is_nan() {
                ctx.cr[crfd] = crate::context::CrField { lt: false, gt: false, eq: false, so: true };
                if fpscr::is_snan(fra) || fpscr::is_snan(frb) {
                    fpscr::set_exception(ctx, fpscr::VXSNAN | fpscr::VXVC);
                } else {
                    fpscr::set_exception(ctx, fpscr::VXVC);
                }
            } else if fra < frb {
                ctx.cr[crfd] = crate::context::CrField { lt: true, gt: false, eq: false, so: false };
            } else if fra > frb {
                ctx.cr[crfd] = crate::context::CrField { lt: false, gt: true, eq: false, so: false };
            } else {
                ctx.cr[crfd] = crate::context::CrField { lt: false, gt: false, eq: true, so: false };
            }
            let fprf = if fra.is_nan() || frb.is_nan() {
                0b0_0001
            } else if fra < frb {
                0b0_1000
            } else if fra > frb {
                0b0_0100
            } else {
                0b0_0010
            };
            fpscr::set_fprf(ctx, fprf);
            ctx.pc += 4;
        }

Special Cases & Edge Conditions

  • Ordered compare. Same CR-field semantics as fcmpu (LT/GT/EQ/SO), but NaN inputs raise additional FPSCR exceptions:
    • Either operand NaN → FPSCR[VXVC] = 1 (invalid-operation: compare on QNaN/SNaN).
    • Either operand signalling NaN → also FPSCR[VXSNAN] = 1.
    • All NaN cases also set FX = 1 and VX = 1.
  • xenia quirk. xenia-rs's fcmpo body is identical to fcmpu — the FPSCR exception bits are not modelled. The xenia source comment explicitly notes "Same as fcmpu but sets FPSCR exception bits for QNaN (not modeled yet)". Title code that polls FPSCR for compare-class invalid-operation will not observe it.
  • CR field bits.
    • LT (bit 0) — FRA < FRB
    • GT (bit 1) — FRA > FRB
    • EQ (bit 2) — FRA == FRB
    • SO (bit 3) — unordered (NaN involved)
  • +0 and -0 compare equal.
  • No Rc bit.
  • FPSCR side effects. Hardware updates FPSCR[FPCC], FX, VX, and (on NaN) VXVC/VXSNAN. xenia-rs only updates the CR field.
  • Use case. Ordered compares are required by C/C++ semantics for <, >, <=, >= (which must signal on NaN per IEEE-754). fcmpu corresponds to the C ==/!= semantics (which do not signal).
  • Encoding. X-form, primary 63, XO 32.
  • fcmpux — unordered compare; identical CR result, no VXVC.
  • mcrf, mcrfs, mfcr — fan-out CR fields after compare.
  • bc, bclr, bcctr — conditional branches consume LT/GT/EQ/SO.
  • fselx — branch-free alternative for single-key compares.
  • mcrfs, mffsx — move FPSCR/CR.

IBM Reference