Files
Sylpheed/tools/ppc-manual/memory/dcbi.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

4.8 KiB
Raw Blame History

dcbi — Data Cache Block Invalidate

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

Assembler Mnemonics

Mnemonic XML entry Flags Description
dcbi dcbi Data Cache Block Invalidate

Syntax

dcbi [RA0], [RB]

Encoding

dcbi — form X

  • Opcode word: 0x7c0003ac
  • Primary opcode (bits 05): 31
  • Extended opcode: 470
  • 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
RA0 dcbi: read Source GPR; when the encoded register number is 0 the operand is the literal 64-bit zero, not r0.
RB dcbi: read Source GPR.

Register Effects

dcbi

  • 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)

; 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

dcbi

Special Cases & Edge Conditions

  • Privileged. Unlike dcbf and dcbst, dcbi is supervisor-only. Executing in problem state raises a privileged-instruction (program) interrupt. Game code never issues dcbi directly; only the kernel.
  • Drops dirty data. The line is removed from cache without writing back, so any modifications that have not already been pushed to memory are lost. Used only when the underlying memory is being repurposed (e.g. DMA window flip, page demap) and stale dirty data would be incorrect.
  • Cache line size. Xenon lines are 128 bytes. The low seven bits of EA are ignored — the operation targets the cache line that contains EA.
  • RA0 semantics. When RA = 0, base is literal zero, so dcbi 0, RB invalidates the line containing address RB.
  • Xenia treats it as a no-op. With no modelled cache, the emulator decodes and advances PC; memory is already authoritative.
  • Sequencing. Not synchronising. Pair with sync when invalidation must precede a subsequent load on another thread.
  • Architecturally subsumed by dcbf for problem state. Userspace that wants "this line is no longer valuable" must use dcbf, accepting the write-back cost.
  • dcbf — flush (write-back + invalidate); the unprivileged alternative.
  • dcbst — write-back without invalidate.
  • dcbz, dcbz128 — allocate-and-zero a line.
  • dcbt, dcbtst — prefetch hints.
  • icbi — instruction-cache analog (also problem-state, not privileged).
  • sync, isync — pair with cache-control ops for ordering.

IBM Reference