Files
Sylpheed/tools/ppc-manual/memory/dcbst.md
sim 84856fc081
All checks were successful
CI / Native — linux (pull_request) Successful in 2h1m57s
CI / WASM — Web (pull_request) Successful in 28m8s
CI / Formatting (pull_request) Successful in 1m26s
docs(ppc-manual): check every xenia-rs claim against Canary's source
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>
2026-09-16 21:52:38 +02:00

5.4 KiB
Raw Blame History

dcbst — Data Cache Block Store

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

Assembler Mnemonics

Mnemonic XML entry Flags Description
dcbst dcbst — Data Cache Block Store

Syntax

dcbst [RA0], [RB]

Encoding

dcbst — form X

  • Opcode word: 0x7c00006c
  • Primary opcode (bits 0–5): 31
  • Extended opcode: 54
  • Synchronising: no
Bits Field Meaning
0–5 OPCD primary opcode
6–10 RT/FRT/VRT destination
11–15 RA/FRA/VRA source A
16–20 RB/FRB/VRB source B
21–30 XO extended opcode (10 bits)
31 Rc record-form flag

Operands

Field Role Description
RA0 dcbst: read Source GPR; when the encoded register number is 0 the operand is the literal 64-bit zero, not r0.
RB dcbst: read Source GPR.

Register Effects

dcbst

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

dcbst

Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_dcbst(PPCHIRBuilder& f, const InstrData& i) {
  if (!cvars::disable_prefetch_and_cachecontrol) {
    Value* ea = CalculateEA_0(f, i.X.RA, i.X.RB);
    f.CacheControl(ea, 128, CacheControlType::CACHE_CONTROL_TYPE_DATA_STORE);
  }
  return 0;
}

Special Cases & Edge Conditions

  • Write-through, no invalidate. If the addressed line is dirty, it is written back to memory; the line itself remains in the cache (clean afterwards). Lighter than dcbf — the cache stays warm.
  • Cache line size. Xenon's line is 128 bytes; the low seven bits of EA are ignored. There is no dcbst128; the operation is sized to the architectural line.
  • RA0 semantics. RA = 0 selects literal zero as base. dcbst 0, RB pushes the line containing address RB to memory.
  • Self-modifying code stage 1. The canonical "patch then run" sequence is stw (modify) → dcbst (push dirty data to memory) → sync → icbi (invalidate I-cache for the same address) → isync. dcbst is preferred over dcbf here because it leaves the data in D-cache for any subsequent normal reads.
  • DMA hand-off. Used before initiating a GPU or DMA read of a buffer the CPU has just written, to ensure memory holds the latest data.
  • Unprivileged. Available from problem state.
  • Canary emits a host hint only. No cache state is simulated: unless the disable_prefetch_and_cachecontrol cvar is set, dcbst becomes a host clflush over the 128-byte cache line, and memory is already authoritative.
  • dcbf — flush + invalidate (heavier alternative).
  • dcbi — invalidate without write-back (privileged).
  • dcbz, dcbz128 — allocate-and-zero.
  • dcbt, dcbtst — prefetch hints.
  • icbi — instruction-cache invalidate, sequenced after dcbst in self-modifying-code recipes.
  • sync, isync — ordering primitives that bracket cache control.

IBM Reference