Bundles state that lives OUTSIDE the xenia-rs repo so a fresh clone on
another machine can be brought up to identical configuration via
migration/setup.sh:
- claude-memory/ ~/.claude/projects/-home-fabi-RE-Project-Sylpheed/memory/
(103 files, 1.1 MB - MEMORY.md + every
project_xenia_rs_*.md from audits
addis_signext through audit-058)
- project-root/dot-claude/ <project-root>/.claude/settings.json
(Stop hook + permissions)
- project-root/ppc-manual/ <project-root>/ppc-manual/
(PowerPC reference docs, 397 files, 3.7 MB)
- project-root/run-canary.sh <project-root>/run-canary.sh
- README.md Human-readable setup checklist
- setup.sh Idempotent installer (also reclones
xenia-canary at pinned HEAD 6de80dffe)
- MANIFEST.md Per-file mapping + per-file-not-bundled
restoration recipe
Excluded from bundle (not shippable via git):
- Sylpheed ISO (7.8 GB; copyright; manual copy required)
- sylpheed.db (395 MB; regenerable from XEX via analysis tooling)
- target/ build artifacts (rebuild on target)
- audit-runs probe firehoses (.log/.stdout/.stderr ~11 GB; rerun if needed)
- audit-runs memory dumps (.bin ~4.5 GB; rerun audit-026/027/029 if needed)
- xenia-canary checkout (setup.sh reclones from
git.mc02.dev/fabi/Xenia-Canary.git at HEAD 6de80dffe)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
7.4 KiB
7.4 KiB
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 0–5):
4 - Extended opcode:
1034 - Synchronising: no
| Bits | Field | Meaning |
|---|---|---|
| 0–5 | OPCD |
primary opcode (4) |
| 6–10 | VRT/VD |
destination vector register |
| 11–15 | VRA/VA |
source A vector register |
| 16–20 | VRB/VB |
source B vector register |
| 21–31 | XO |
extended opcode (11 bits) |
vmaxfp128 — form VX128
- Opcode word:
0x18000280 - Primary opcode (bits 0–5):
6 - Extended opcode:
640 - Synchronising: no
| Bits | Field | Meaning |
|---|---|---|
| 0–5 | OPCD |
primary opcode (4 or 5) |
| 6–10 | VD128l |
destination low 5 bits |
| 11–15 | VA128l |
source A low 5 bits |
| 16–20 | VB128l |
source B low 5 bits |
| 21 | VA128H |
source A high bit |
| 22 | — |
reserved |
| 23–25 | VC |
optional VC / XO sub-field |
| 26 | VA128h |
source A middle bit |
| 27 | — |
reserved |
| 28–29 | VD128h |
destination high 2 bits |
| 30–31 | 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)
; 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
vmaxfp
- xenia-canary XML:
tools/ppc-instructions.xml— search formnem="vmaxfp" - xenia-canary emit:
src/xenia/cpu/ppc/ppc_emit_altivec.cc:831 - xenia-rs opcode:
crates/xenia-cpu/src/opcode.rs:101 - xenia-rs decoder:
crates/xenia-cpu/src/decoder.rs:522 - xenia-rs interpreter:
crates/xenia-cpu/src/interpreter.rs:2121-2128
xenia-rs interpreter body (frozen snapshot)
PpcOpcode::vmaxfp => {
let a = ctx.vr[instr.ra()].as_f32x4();
let b = ctx.vr[instr.rb()].as_f32x4();
let mut r = [0f32; 4];
for i in 0..4 { r[i] = vmx::max_nan(a[i], b[i]); }
ctx.vr[instr.rd()] = xenia_types::Vec128::from_f32x4_array(r);
ctx.pc += 4;
}
vmaxfp128
- xenia-canary XML:
tools/ppc-instructions.xml— search formnem="vmaxfp128" - xenia-canary emit:
src/xenia/cpu/ppc/ppc_emit_altivec.cc:834 - xenia-rs opcode:
crates/xenia-cpu/src/opcode.rs:101 - xenia-rs decoder:
crates/xenia-cpu/src/decoder.rs:696 - xenia-rs interpreter:
crates/xenia-cpu/src/interpreter.rs:2129-2136
xenia-rs interpreter body (frozen snapshot)
PpcOpcode::vmaxfp128 => {
let a = ctx.vr[instr.va128()].as_f32x4();
let b = ctx.vr[instr.vb128()].as_f32x4();
let mut r = [0f32; 4];
for i in 0..4 { r[i] = vmx::max_nan(a[i], b[i]); }
ctx.vr[instr.vd128()] = xenia_types::Vec128::from_f32x4_array(r);
ctx.pc += 4;
}
Special Cases & Edge Conditions
- Per-lane IEEE max. Four word lanes;
VD[i] = (VA[i] > VB[i]) ? VA[i] : VB[i]. - NaN propagation surprise. Xenia uses
if a > b { a } else { b }, so any NaN comparison evaluates false and the result isVB. The IBM manual specifies "the larger ofVA[i]andVB[i], with NaN handling such that any NaN input yields a NaN result" — this is not what xenia does. Hardware'svmaxfp(NaN, x) = NaNwhile xenia returnsx. Worth checking againstvmx.rsfor any future correctness fixes. - Sign of zero.
vmaxfp(+0, -0)returns-0in xenia (since+0 > -0is false → returnsb = -0). The hardware likely returns the sign-positive zero — also worth verifying. VSCR[NJ]denormals. WithNJ = 1(Xenon default), denormal inputs are flushed to±0before 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, v4is the standard "clamp from below byv4" idiom. - VMX128 sibling (
vmaxfp128). Identical comparator semantics with the extended encoding.
Related Instructions
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.