Files
Sylpheed/tools/ppc-manual/fpu/fabsx.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.7 KiB
Raw Blame History

fabsx — Floating Absolute Value

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

Assembler Mnemonics

Mnemonic XML entry Flags Description
fabs fabsx Floating Absolute Value
fabs. fabsx Rc=1 Floating Absolute Value

Syntax

fabs[Rc] [FD], [FB]

Encoding

fabsx — form X

  • Opcode word: 0xfc000210
  • Primary opcode (bits 05): 63
  • Extended opcode: 264
  • 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
FB fabsx: read Source B floating-point register.
FD fabsx: write Destination floating-point register.
CR fabsx: 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

fabsx

  • Reads (always): FB
  • Reads (conditional): none
  • Writes (always): FD
  • Writes (conditional): CR

Status-Register Effects

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

Operation (pseudocode)

FRT <- clear_sign(FRB)

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

fabsx

Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_fabsx(PPCHIRBuilder& f, const InstrData& i) {
  // frD <- abs(frB)
  Value* v = f.Abs(f.LoadFPR(i.X.RB));
  f.StoreFPR(i.X.RT, v);
  /*
  The contents of frB with bit 0 cleared are placed into frD.
Note that the fabs instruction treats NaNs just like any other kind of value.
That is, the sign bit of a NaN may be altered by fabs. This instruction does not
alter the FPSCR. Other registers altered: • Condition Register (CR1 field):
Affected: FX, FEX, VX, OX (if Rc = 1)
  */
  // f.UpdateFPSCR(v, i.X.Rc);
  if (i.X.Rc) {
    // todo
  }
  return 0;
}

Special Cases & Edge Conditions

  • Bit-pattern operation, no rounding. fabs clears the sign bit (bit 0) of the source FPR's binary64 representation and writes the 64-bit value to the destination unchanged otherwise. No precision loss, no FPSCR exception bits. The mnemonic does not have an s variant — there is one form regardless of whether the operand is interpreted as binary32 or binary64.
  • NaN handling. fabs(NaN) returns the same NaN with the sign bit cleared. The signalling/quiet bit is not modified, and FPSCR[VXSNAN] is not raised. Canary emits f.Abs, a pure sign-bit clear. ⚠️ Its Rc=1 branch is empty, so fabs. does not update CR1 in Canary.
  • Special values. fabs(±0) = +0; fabs(±∞) = +∞; fabs(±NaN) = +NaN (sign cleared, payload preserved).
  • FPSCR is largely untouched. Hardware specifies FPRF is not updated by fabs, and no exception bits are raised. Notation in the page header about FPSCR write is generic — the only meaningful write is via Rc=1.
  • Rc=1 (fabs.) copies FPSCR[FX, FEX, VX, OX] into CR1 (these bits are typically stale or zero).
  • No FRA operand. X-form, primary 63, XO 264. Reads FRB only; bits 1115 are don't-care.
  • Common idiom. fabs followed by fcmpu against a small constant for ULP-sized "near zero" tests; or paired with fneg/fnabs for sign-set-to-known operations.
  • fnegx — flip sign bit.
  • fnabsx — absolute value with sign set (always negative result).
  • fmrx — copy FPR (no sign manipulation).
  • fselx — branch-free select; combined with fabs for min/max/clamp patterns.
  • fcmpux, fcmpox — compares often paired with fabs for magnitude tests.

IBM Reference