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>
5.3 KiB
5.3 KiB
dcbt — Data Cache Block Touch
Assembler Mnemonics
| Mnemonic | XML entry | Flags | Description |
|---|---|---|---|
dcbt |
dcbt |
— | Data Cache Block Touch |
Syntax
dcbt [RA0], [RB]
Encoding
dcbt — form X
- Opcode word:
0x7c00022c - Primary opcode (bits 0–5):
31 - Extended opcode:
278 - 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 |
dcbt: read | Source GPR; when the encoded register number is 0 the operand is the literal 64-bit zero, not r0. |
RB |
dcbt: read | Source GPR. |
Register Effects
dcbt
- 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
dcbt
- Canary XML:
tools/ppc-instructions.xml— search formnem="dcbt" - Canary emitter:
src/xenia/cpu/ppc/ppc_emit_memory.cc:1142 - Sylpheed opcode:
crates/sylpheed-ppc/src/opcode.rs:47 - Sylpheed decoder:
crates/sylpheed-ppc/src/decoder.rs:909
Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_dcbt(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_TOUCH);
}
return 0;
}
Special Cases & Edge Conditions
- Hint, not a guarantee.
dcbtrequests that the cache line containingEAbe brought into L1 in anticipation of a future load. The processor is free to ignore the hint (e.g. under cache pressure or for non-cacheable storage). - Read-intent prefetch. Pair-mate of
dcbtst(which signals write intent and may prefer an exclusive cache state). Usedcbtwhen the next access is a read. - No exception on bad address. Unlike a real load,
dcbtto an unmapped or protected page does not raise; the hint is silently dropped. This makes it safe to "speculatively" prefetch one line past the end of a buffer. - Cache line size. Xenon line is 128 bytes; low seven bits of
EAare ignored. RA0semantics.RA = 0selects literal zero —dcbt 0, RBprefetches the line containing addressRB.- Stream-engine hints. The Xenon supports up to four hardware data-streams set up by sequences of
dcbtwith a stride; refer to the XDK for the stream-engine encoding (uses bits ignored by the architectural decode). - Canary turns it into a host hint. Unless
disable_prefetch_and_cachecontrolis set it emitsprefetcht0over the 128-byte cache line. Hints have no guest-observable effect. - Unprivileged. Always available.
Related Instructions
dcbtst— write-intent prefetch.dcbf,dcbst,dcbi— push / invalidate counterparts.dcbz,dcbz128— allocate-and-zero (a stronger "I want this line" signal).icbi— instruction-cache analog (no instruction-cache prefetch in PowerPC).
IBM Reference
- AIX 7.3 —
dcbt(Data Cache Block Touch) PowerISA v2.07B Book II§ "Storage Control Instructions" for hint semantics.