Files
Sylpheed/tools/ppc-manual/memory/stvebx.md
MechaCat02 6bdbf89ebc
All checks were successful
CI / Native — linux (pull_request) Successful in 37m56s
CI / WASM — Web (pull_request) Successful in 28m5s
CI / Formatting (pull_request) Successful in 59s
chore(tools): adopt the PPC manual and a canary launcher that works anywhere
CONSOLIDATION.md Phase 6. Both lived untracked in the project root -- on one
disk, backed up by nothing.

  tools/ppc-manual/   393 files, 3.7 MB. 455 instructions, 350 family pages,
                      598 mnemonics resolvable through index.json, plus the
                      generator that produced them.
  tools/run-canary.sh the oracle launcher.

🔴 THE LAUNCHER WAS BROKEN IN TWO WAYS AND IS REWRITTEN, not copied:

  * it pointed at `xenia-rs/sylpheed.iso`, a SYMLINK. Wine cannot resolve one
    and says "path invalid", which reads as a corrupt image rather than a path
    problem -- it has cost a session before. It now points at the real file and
    warns if handed a symlink.
  * it hardcoded one machine's absolute paths, and named `xenia-rs`, which this
    consolidation retires. Now derived from the script's own location, with
    SYLPH_CANARY_BIN / SYLPH_ISO overrides and a check that each exists.

The standing constraints are in its header where someone will read them: one
emulator at a time, Canary runs MUTED, and never judge a crash or a hang from
a Bash-launched run -- a SIGKILL that looked like the binary was the editor's
process supervisor.

⚠️ The manual's GENERATOR reads the xenia-rs source tree, which is going away.
Its decoder now lives here as crates/sylpheed-ppc, so the generator must be
repointed before it is run again. Recorded in the README rather than left for
someone to discover; the manual's content is checked in and regenerates from
nothing implicitly.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-13 21:18:00 +02:00

5.9 KiB
Raw Blame History

stvebx — Store Vector Element Byte Indexed

Category: Memory · Form: X · Opcode: 0x7c00010e

Assembler Mnemonics

Mnemonic XML entry Flags Description
stvebx stvebx Store Vector Element Byte Indexed

Syntax

stvebx [VS], [RA0], [RB]

Encoding

stvebx — form X

  • Opcode word: 0x7c00010e
  • Primary opcode (bits 05): 31
  • Extended opcode: 135
  • 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
VS stvebx: read Source vector register (alias for VD on stores).
RA0 stvebx: read Source GPR; when the encoded register number is 0 the operand is the literal 64-bit zero, not r0.
RB stvebx: read Source GPR.

Register Effects

stvebx

  • Reads (always): VS, RA0, RB
  • Reads (conditional): none
  • Writes (always): none
  • 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

stvebx

xenia-rs interpreter body (frozen snapshot)
        PpcOpcode::stvebx => {
            // Store vS[EA & 0xF] (1 byte) to memory at EA.
            let base = if instr.ra() == 0 { 0u64 } else { ctx.gpr[instr.ra()] };
            let ea = base.wrapping_add(ctx.gpr[instr.rb()]) as u32;
            // PPCBUG-512: stvebx was missing invalidate_for_write.
            if let Some(t) = ctx.reservation_table.as_ref().filter(|t| t.is_enabled()) {
                if t.has_active_reservers() { t.invalidate_for_write(ea); }
            }
            let slot = (ea & 0xF) as usize;
            let bytes = ctx.vr[instr.rs()].as_bytes();
            mem.write_u8(ea, bytes[slot]);
            ctx.pc += 4;
        }

Special Cases & Edge Conditions

  • Single-byte element store. Architecturally stvebx writes exactly one byte from lane EA mod 16 of VS to address EA. Other lanes are unaffected, and other memory bytes are unaffected.
  • Xenia simplification — full 16-byte write. The xenia snapshot is shared with stvehx / stvewx and writes the entire 16-byte aligned line (ea & ~0xF, then 16 bytes from the vector). This is stronger than the architectural single-byte store — it overwrites 15 adjacent bytes with whatever the source vector holds. Code that depends on architectural per-byte granularity (e.g. interleaved writes from multiple threads / DMA agents into the same line) may behave differently than on hardware.
  • RA0 semantics. RA = 0 selects literal zero.
  • No update form, no VMX128 sibling. No stvebux; no stvebx128 — single-byte stores were kept Altivec-only in the Xbox 360 extension.
  • Big-endian within the line. Lane 0 of VS corresponds to the byte at the aligned base address.
  • Common idiom. Pair with vsplt* to broadcast a value, then stvebx to write one byte. Less efficient than stb from a GPR; rare in compiled code.
  • Hardware fault model. A protected or unmapped page raises a DSI exception just as for any store.
  • stvehx, stvewx — single half / single word element stores.
  • stvx, stvxl — full 16-byte aligned vector stores.
  • stvlx, stvrx — store-left / store-right unaligned vector ops.
  • lvebx — symmetric single-byte load.

IBM Reference