Files
Sylpheed/tools/ppc-manual/fpu/fdivx.md
sim 9bfe96e44d fix(ppc-manual): 543 dead links, from two generator bugs and wrong relative paths
- Category pages linked each family as `<slug>.md`, relative to categories/,
  where no family page lives. They now link `../<category>/<slug>.md`.
- Form pages linked a member into its *own* category directory, so every
  VMX128 sibling (`vsldoi128`) pointed at vmx128/ although its family page is
  under vmx/. They now link into the family's directory.
- Hand-written "Related" and sibling mentions linked other categories' pages
  as if they were in the same directory. 109 are retargeted through the page
  index; 29 that pointed a family page at itself (`vrefp128` on vrefp.md) and
  6 naming instructions the manual has no page for are plain text now.

Regenerated at the existing Canary pin (f21ebd49e): upstream has moved on, and
re-pinning belongs in its own change. The generator reports 0 family pages
changed and is idempotent; the only dead links left are TEMPLATE.md's
placeholders.

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

6.1 KiB
Raw Blame History

fdivx — Floating Divide

Category: Floating-Point · Form: A · Opcode: 0xfc000024

Assembler Mnemonics

Mnemonic XML entry Flags Description
fdiv fdivx Floating Divide
fdiv. fdivx Rc=1 Floating Divide

Syntax

fdiv[Rc] [FD], [FA], [FB]

Encoding

fdivx — form A

  • Opcode word: 0xfc000024
  • Primary opcode (bits 05): 63
  • Extended opcode: 18
  • Synchronising: no
Bits Field Meaning
05 OPCD primary opcode (59 or 63)
610 FRT destination FPR
1115 FRA source A FPR
1620 FRB source B FPR
2125 FRC source C FPR (multiplier for madd-style ops)
2630 XO extended opcode (5 bits)
31 Rc record-form flag (updates CR1)

Operands

Field Role Description
FA fdivx: read Source A floating-point register (fr0fr31).
FB fdivx: read Source B floating-point register.
FD fdivx: write Destination floating-point register.
CR fdivx: write (conditional) Condition-register update. When Rc=1, CR field 0 (or CR6 for vector compares, CR1 for FPU) is updated from the result.
FPSCR fdivx: write Floating-Point Status and Control Register.

Register Effects

fdivx

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

Status-Register Effects

  • fdivx: CR1 ← FPSCR[FX, FEX, VX, OX] when Rc=1.; FPSCR updated per IEEE-754 flags (FX, FEX, FPRF, FR, FI, exceptions).

Operation (pseudocode)

FRT <- FRA ÷ 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

fdivx

Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_fdivx(PPCHIRBuilder& f, const InstrData& i) {
  // frD <- frA / frB
#if XE_PLATFORM_LINUX
  // TODO(has207): verify if this is needed on Windows
  // On Linux, fdiv needs to use A format fields instead of X format
  Value* v = f.Div(f.LoadFPR(i.A.FRA), f.LoadFPR(i.A.FRB));
  f.StoreFPR(i.A.FRT, v);
  f.UpdateFPSCR(v, i.A.Rc);
#else
  Value* v = f.Div(f.LoadFPR(i.X.RA), f.LoadFPR(i.X.RB));
  f.StoreFPR(i.X.RT, v);
  f.UpdateFPSCR(v, i.X.Rc);
#endif
  return 0;
}

Special Cases & Edge Conditions

  • Double precision. Operates on IEEE-754 binary64; fdivsx is the single-precision sibling.
  • Divide by zero. FRA / ±0 (with FRA finite, non-zero) sets FPSCR[ZX, FX] and produces a correctly-signed infinity. Canary's vdivsd produces the same ±∞ — but does not raise ZX (UpdateFPSCR is a stub). Canary quirk: title code that polls FPSCR for divide-by-zero will not observe it.
  • 0 / 0 sets FPSCR[VXZDZ, VX, FX] and yields a quiet NaN.
  • ±∞ / ±∞ sets FPSCR[VXIDI, VX, FX] and yields a quiet NaN.
  • FPSCR side effects. Hardware updates FPRF, FR, FI, FX plus exception bits OX, UX, XX, ZX, VXZDZ, VXIDI, VXSNAN. Canary does not maintain these: its UpdateFPSCR is a stub that clears FEX/VX and, with Rc=1, writes CR1 as all zeros.
  • Rc=1 (fdiv.) copies FPSCR[FX, FEX, VX, OX] into CR1.
  • NaN propagation. Quiet-NaN result for any NaN operand; signalling NaNs are quietened.
  • Performance. Hardware divide is multi-cycle and not pipelined on Xenon. Many titles prefer fres/frsqrte followed by Newton-Raphson refinement (or by fmadd chains) to avoid the divider.
  • Denormal flush. That Xenon boots with FPSCR[NI]=1 is unverified. Canary starts every guest thread in IEEE mode (MXCSR 0x1F80; its init comment flags the startup state as unchecked) and turns on the host's flush-to-zero (MXCSR.FZ) only when the guest sets NI through mtfsf/mtfsfi.
  • Encoding. A-form, primary 63, XO 18. FRC is don't-care.
  • fdivsx — single-precision divide.
  • fresx — reciprocal estimate ~1/FRB; combined with fmul/fmadd to implement reciprocal divides.
  • fmulx, faddx, fsubx — companion arithmetic.
  • fmaddx, fnmsubx — used in Newton-Raphson refinement steps.
  • mffsx, mtfsfx — FPSCR control (rounding mode, exception masks).

IBM Reference