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>
4.9 KiB
4.9 KiB
dcbi — Data Cache Block Invalidate
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 0–5):
31 - Extended opcode:
470 - 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 |
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)
; 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
dcbi
- Canary XML:
tools/ppc-instructions.xml— search formnem="dcbi" - Sylpheed opcode:
crates/sylpheed-ppc/src/opcode.rs:45 - Sylpheed decoder:
crates/sylpheed-ppc/src/decoder.rs:926
Special Cases & Edge Conditions
- Privileged. Unlike
dcbfanddcbst,dcbiis supervisor-only. Executing in problem state raises a privileged-instruction (program) interrupt. Game code never issuesdcbidirectly; 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
EAare ignored — the operation targets the cache line that containsEA. RA0semantics. WhenRA = 0, base is literal zero, sodcbi 0, RBinvalidates the line containing addressRB.- Canary does not implement it.
dcbiis in its opcode table but has no emitter, so translating one logs "Unimplemented instr" and, with the defaultbreak_on_unimplemented_instructions, breaks. - Sequencing. Not synchronising. Pair with
syncwhen invalidation must precede a subsequent load on another thread. - Architecturally subsumed by
dcbffor problem state. Userspace that wants "this line is no longer valuable" must usedcbf, accepting the write-back cost.
Related Instructions
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
- AIX 7.3 —
dcbi(Data Cache Block Invalidate) PowerISA v2.07B Book IIfor the privilege model and cache-coherence rules.