Files
Sylpheed/tools/ppc-manual/vmx/vmaxfp.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

7.4 KiB
Raw Permalink Blame History

vmaxfp — Vector Maximum Floating Point

Category: VMX (Altivec) · Form: VX · Opcode: 0x1000040a

Assembler Mnemonics

Mnemonic XML entry Flags Description
vmaxfp vmaxfp Vector Maximum Floating Point
vmaxfp128 vmaxfp128 Vector128 Maximum Floating Point

Syntax

vmaxfp [VD], [VA], [VB]
vmaxfp128 [VD], [VA], [VB]

Encoding

vmaxfp — form VX

  • Opcode word: 0x1000040a
  • Primary opcode (bits 05): 4
  • Extended opcode: 1034
  • Synchronising: no
Bits Field Meaning
05 OPCD primary opcode (4)
610 VRT/VD destination vector register
1115 VRA/VA source A vector register
1620 VRB/VB source B vector register
2131 XO extended opcode (11 bits)

vmaxfp128 — form VX128

  • Opcode word: 0x18000280
  • Primary opcode (bits 05): 6
  • Extended opcode: 640
  • Synchronising: no
Bits Field Meaning
05 OPCD primary opcode (4 or 5)
610 VD128l destination low 5 bits
1115 VA128l source A low 5 bits
1620 VB128l source B low 5 bits
21 VA128H source A high bit
22 reserved
2325 VC optional VC / XO sub-field
26 VA128h source A middle bit
27 reserved
2829 VD128h destination high 2 bits
3031 VB128h source B high 2 bits

Operands

Field Role Description
VA vmaxfp: read; vmaxfp128: read Source A vector register.
VB vmaxfp: read; vmaxfp128: read Source B vector register.
VD vmaxfp: write; vmaxfp128: write Destination vector register.

Register Effects

vmaxfp

  • Reads (always): VA, VB
  • Reads (conditional): none
  • Writes (always): VD
  • Writes (conditional): none

vmaxfp128

  • Reads (always): VA, VB
  • Reads (conditional): none
  • Writes (always): VD
  • Writes (conditional): none

Status-Register Effects

No condition-register or status-register effects.

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

vmaxfp

Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_vmaxfp(PPCHIRBuilder& f, const InstrData& i) {
  return InstrEmit_vmaxfp_(f, i.VX.VD, i.VX.VA, i.VX.VB);
}

// ── delegates to (src/xenia/cpu/ppc/ppc_emit_altivec.cc:812) ──
int InstrEmit_vmaxfp_(PPCHIRBuilder& f, uint32_t vd, uint32_t va, uint32_t vb) {
  // (VD) <- max((VA), (VB))
  Value* v = f.Max(f.LoadVR(va), f.LoadVR(vb));
  f.StoreVR(vd, v);
  return 0;
}

vmaxfp128

Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_vmaxfp128(PPCHIRBuilder& f, const InstrData& i) {
  return InstrEmit_vmaxfp_(f, VX128_VD128, VX128_VA128, VX128_VB128);
}

// ── delegates to (src/xenia/cpu/ppc/ppc_emit_altivec.cc:812) ──
int InstrEmit_vmaxfp_(PPCHIRBuilder& f, uint32_t vd, uint32_t va, uint32_t vb) {
  // (VD) <- max((VA), (VB))
  Value* v = f.Max(f.LoadVR(va), f.LoadVR(vb));
  f.StoreVR(vd, v);
  return 0;
}

Special Cases & Edge Conditions

  • Per-lane IEEE max. Four word lanes; VD[i] = (VA[i] > VB[i]) ? VA[i] : VB[i].
  • NaN propagation. The IBM manual specifies "the larger of VA[i] and VB[i], with NaN handling such that any NaN input yields a NaN result". Canary's x64 MAX matches: it blends the NaN back in when either lane is NaN (VA's when both are), and takes max(+0, 0) = +0 by AND-ing both operand orders of vmaxps.
  • Sign of zero. Canary's vmaxfp(+0, -0) returns +0: it ANDs both operand orders of vmaxps (its comment: "if 0 and -0, return 0! opposite of minfp"). What Xenon returns is unverified.
  • VSCR[NJ] denormals. With NJ = 1 (Xenon default), denormal inputs are flushed to ±0 before comparison.
  • No VSCR[SAT] change, no XER change, no exceptions.
  • Big-endian word lanes. Lane 0 is the most-significant word.
  • Aliasing legal. vmaxfp v3, v3, v4 is the standard "clamp from below by v4" idiom.
  • VMX128 sibling (vmaxfp128). Identical comparator semantics with the extended encoding.
  • vminfp — the per-lane minimum.
  • vcmpgtfp, vcmpgefp — separate compare-and-mask path.
  • vsel — combine masks with arbitrary alternatives.
  • vmaddfp — fused multiply-add when the max is part of a polynomial.
  • vmaxsw — integer-word max if the lanes are signed integers.

IBM Reference