Files
xenia-rs/migration/project-root/ppc-manual/vmx/vaddsws.md
MechaCat02 e6d43a23ac chore: add migration/ bundle for cross-machine setup
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>
2026-05-10 21:38:38 +02:00

5.9 KiB
Raw Permalink Blame History

vaddsws — Vector Add Signed Word Saturate

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

Assembler Mnemonics

Mnemonic XML entry Flags Description
vaddsws vaddsws Vector Add Signed Word Saturate

Syntax

vaddsws [VD], [VA], [VB]

Encoding

vaddsws — form VX

  • Opcode word: 0x10000380
  • Primary opcode (bits 05): 4
  • Extended opcode: 896
  • 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)

Operands

Field Role Description
VA vaddsws: read Source A vector register.
VB vaddsws: read Source B vector register.
VD vaddsws: write Destination vector register.
VSCR vaddsws: write Vector Status and Control Register (NJ/SAT bits).

Register Effects

vaddsws

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

Status-Register Effects

  • vaddsws: VSCR[SAT] may be stickied on saturating vector operations.

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

vaddsws

xenia-rs interpreter body (frozen snapshot)
        PpcOpcode::vaddsws => {
            let a = crate::vmx::as_i32x4(ctx.vr[instr.ra()]);
            let b = crate::vmx::as_i32x4(ctx.vr[instr.rb()]);
            let mut r = [0i32; 4]; let mut sat = false;
            for i in 0..4 {
                let (v, s) = crate::vmx::sat_add_i32(a[i], b[i]);
                r[i] = v; sat |= s;
            }
            if sat { ctx.set_vscr_sat(true); }
            ctx.vr[instr.rd()] = crate::vmx::from_i32x4(r);
            ctx.pc += 4;
        }

Special Cases & Edge Conditions

  • Four signed-word lanes, saturating. Each VD[i] = clamp(VA[i] + VB[i], INT32_MIN, INT32_MAX) for i = 0..3. Lane 0 (VD[0..3] after stvx) is the most-significant word.
  • VSCR[SAT] is sticky-set if any lane clamps. Xenia tracks this through crate::vmx::sat_add_i32 (crates/xenia-cpu/src/vmx.rs) and ORs the flag into the architectural VSCR[SAT].
  • No multi-precision carry. Unlike vaddcuw, vaddsws does not expose a per-lane carry/borrow — a saturated lane simply clips; it does not overflow into the adjacent lane.
  • Asymmetric clamp. INT32_MAX + 1 = INT32_MAX; INT32_MIN + (-1) = INT32_MIN.
  • The modulo sibling is vadduwm. Modulo add for signed and unsigned words is bit-identical; switch to vaddsws only when clipping with sign awareness is desired.
  • No XER side effects.
  • No VMX128 sibling.
  • Common usage. Accumulate four 32-bit signed sums per cycle (e.g. dot products of int16 lanes after a vmsumshs — which already saturates internally — for further accumulation across multiple iterations).
  • vadduws — same width, unsigned saturating add.
  • vadduwm — same width, modulo (non-saturating) add; sign-agnostic.
  • vaddsbs, vaddshs — signed saturating add at byte / half width.
  • vsubsws — the matching signed saturating subtract.
  • vmsumshs, vmsumuhs — saturating multiply-sum that often feeds a vaddsws chain.
  • mtvscr / mfvscr — read or clear the VSCR[SAT] bit.

IBM Reference