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>
4.8 KiB
4.8 KiB
vupkhpx — Vector Unpack High Pixel
Category: VMX (Altivec) · Form: VX · Opcode:
0x1000034e
Assembler Mnemonics
| Mnemonic | XML entry | Flags | Description |
|---|---|---|---|
vupkhp |
vupkhpx |
— | Vector Unpack High Pixel |
Syntax
vupkhpx [VD], [VB]
Encoding
vupkhpx — form VX
- Opcode word:
0x1000034e - Primary opcode (bits 0–5):
4 - Extended opcode:
846 - 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) |
Operands
| Field | Role | Description |
|---|---|---|
VB |
vupkhpx: read | Source B vector register. |
VD |
vupkhpx: write | Destination vector register. |
Register Effects
vupkhpx
- Reads (always):
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
vupkhpx
- Canary XML:
tools/ppc-instructions.xml— search formnem="vupkhpx" - Canary emitter:
src/xenia/cpu/ppc/ppc_emit_altivec.cc:1988 - Sylpheed opcode:
crates/sylpheed-ppc/src/opcode.rs:486 - Sylpheed decoder:
crates/sylpheed-ppc/src/decoder.rs:626
Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_vupkhpx(PPCHIRBuilder& f, const InstrData& i) {
XEINSTRNOTIMPLEMENTED();
return 1;
}
Special Cases & Edge Conditions
- Unpack the high 4 of 8 pixel half-words. The upper half-words of
VB(VB.h[0..3]) are each decoded from 1-5-5-5 pixel format into a 32-bit word (1.5.5.5 → 1.8.8.8with sign-extension on the alpha bit and zero-extension of each colour channel into the high 5 bits of a byte). ⚠️ Canary does not implementvupkhpx: its emitter isXEINSTRNOTIMPLEMENTED, so translating one logs "Unimplemented instr" and, with the defaultbreak_on_unimplemented_instructions, breaks. - Output layout.
VD.w[0..3]receive the 4 decoded pixels in big-endian order. - Inverse of the high half of
vpkpx. Unpacking loses no information beyond what the 1-5-5-5 format allows. - No saturation, no flags, no VSCR.
- No VMX128 sibling. VMX128 code uses
vupkd3d128for richer D3D formats.
Related Instructions
vupklpx— unpack the low 4 pixel half-words.vpkpx— the inverse pack.vupkhsb,vupklsb— byte → half-word sign-extending unpacks.vupkhsh,vupklsh— half-word → word sign-extending unpacks.vupkd3d128— VMX128 D3D-format unpack.