- Category pages linked each family as `<slug>.md`, relative to categories/, where no family page lives. They now link `../<category>/<slug>.md`. - Form pages linked a member into its *own* category directory, so every VMX128 sibling (`vsldoi128`) pointed at vmx128/ although its family page is under vmx/. They now link into the family's directory. - Hand-written "Related" and sibling mentions linked other categories' pages as if they were in the same directory. 109 are retargeted through the page index; 29 that pointed a family page at itself (`vrefp128` on vrefp.md) and 6 naming instructions the manual has no page for are plain text now. Regenerated at the existing Canary pin (f21ebd49e): upstream has moved on, and re-pinning belongs in its own change. The generator reports 0 family pages changed and is idempotent; the only dead links left are TEMPLATE.md's placeholders. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
5.8 KiB
5.8 KiB
vaddsbs — Vector Add Signed Byte Saturate
Category: VMX (Altivec) · Form: VX · Opcode:
0x10000300
Assembler Mnemonics
| Mnemonic | XML entry | Flags | Description |
|---|---|---|---|
vaddsbs |
vaddsbs |
— | Vector Add Signed Byte Saturate |
Syntax
vaddsbs [VD], [VA], [VB]
Encoding
vaddsbs — form VX
- Opcode word:
0x10000300 - Primary opcode (bits 0–5):
4 - Extended opcode:
768 - 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 |
|---|---|---|
VA |
vaddsbs: read | Source A vector register. |
VB |
vaddsbs: read | Source B vector register. |
VD |
vaddsbs: write | Destination vector register. |
VSCR |
vaddsbs: write | Vector Status and Control Register (NJ/SAT bits). |
Register Effects
vaddsbs
- Reads (always):
VA,VB - Reads (conditional): none
- Writes (always):
VD,VSCR - Writes (conditional): none
Status-Register Effects
vaddsbs: VSCR[SAT] may be stickied on saturating vector operations.
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
vaddsbs
- Canary XML:
tools/ppc-instructions.xml— search formnem="vaddsbs" - Canary emitter:
src/xenia/cpu/ppc/ppc_emit_altivec.cc:348 - Sylpheed opcode:
crates/sylpheed-ppc/src/opcode.rs:298 - Sylpheed decoder:
crates/sylpheed-ppc/src/decoder.rs:613
Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_vaddsbs(PPCHIRBuilder& f, const InstrData& i) {
Value* v = f.VectorAdd(f.LoadVR(i.VX.VA), f.LoadVR(i.VX.VB), INT8_TYPE,
ARITHMETIC_SATURATE);
f.StoreSAT(f.DidSaturate(v));
f.StoreVR(i.VX.VD, v);
return 0;
}
Special Cases & Edge Conditions
- Sixteen signed-byte lanes, saturating. Each
VD[i] = clamp(VA[i] + VB[i], -128, +127)fori = 0..15, with both inputs interpreted as signedint8. Lane 0 is the most-significant byte (the byte at the lowest address afterstvx). VSCR[SAT]is sticky-set when any lane saturates — either positively (overflow above+127) or negatively (underflow below-128). The SAT bit is never cleared by this op; software must usemtvscrto clear it. ⚠️ Canary never recordsSAT: itsStoreSAT(DidSaturate(v))writes a privatevscr_satbyte, the x64DID_SATURATEis a stub that always yields 0, andmfvscrreadsvscr_vec, which onlymtvscrchanges.- Compare with the modulo sibling.
vaddubmis bit-pattern-identical to a hypotheticalvaddsbmand silently wraps without touchingVSCR[SAT]. Usevaddsbswhenever clipping is desired and you need the sticky overflow flag. - Asymmetric clamp.
+127 + 1 = +127;-128 + (-1) = -128. Tests that look for "any saturation" should mask both saturation directions. - No XER side effects. Altivec never updates
XER[CA]/XER[OV]. The only status bit affected isVSCR[SAT]. - Aliasing legal.
vaddsbs v3, v3, v4is the standard accumulate idiom for a clamping sum. - No VMX128 sibling.
Related Instructions
vaddubs— same width, unsigned saturating add (clamps to0..255).vaddubm— same width, modulo (non-saturating) add; sign-agnostic.vaddshs,vaddsws— signed saturating add at half / word width.vsubsbs— the matching signed saturating subtract.mtvscr/mfvscr— read or clear the stickyVSCR[SAT]bit observed here.