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.6 KiB
4.6 KiB
sync — Synchronize
Category: Integer ALU · Form: X · Opcode:
0x7c0004ac
Assembler Mnemonics
| Mnemonic | XML entry | Flags | Description |
|---|---|---|---|
sync |
sync |
— | Synchronize |
Syntax
sync
Encoding
sync — form X
- Opcode word:
0x7c0004ac - Primary opcode (bits 0–5):
31 - Extended opcode:
598 - 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 |
|---|
Register Effects
sync
- Reads (always): none
- Reads (conditional): none
- Writes (always): none
- Writes (conditional): none
Status-Register Effects
No condition-register or status-register effects.
Operation (pseudocode)
multi-thread memory barrier (heavy). L=0 full sync; L=1 lightweight sync.
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
sync
- Canary XML:
tools/ppc-instructions.xml— search formnem="sync" - Canary emitter:
src/xenia/cpu/ppc/ppc_emit_memory.cc:754 - Sylpheed opcode:
crates/sylpheed-ppc/src/opcode.rs:288 - Sylpheed decoder:
crates/sylpheed-ppc/src/decoder.rs:940
Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_sync(PPCHIRBuilder& f, const InstrData& i) {
f.MemoryBarrier();
return 0;
}
Special Cases & Edge Conditions
- Heavy multi-thread memory barrier. All memory accesses (loads and stores, cacheable and not) issued by this thread before
synccomplete with respect to all other threads/processors before any subsequent memory access begins. Drains the store queue. Lfield selects sync class.L=0is full hwsync (the default).L=1islwsync— orders only loads-after-loads, loads-after-stores, and stores-after-stores (not stores-after-loads). The Xenon implements both via the same encoding withL(bit 9) selecting variant. Most disassembly shows the unsuffixedsyncmnemonic, which assembles toL=0.- No register or CR effects. Pure ordering primitive.
- Used to implement release semantics. A typical lock-release sequence is
sync; stw r0, lock. Acquire side useslwsyncafter the load. - Canary emits
f.MemoryBarrier(), as foreieio;isyncis a plainf.Nop(). A sequential C translation needs neither: host program order subsumes the PPC ordering. - Distinct from
isync, which orders the instruction stream —syncdoes not refetch instructions. - Slow on real hardware. Hundreds of cycles when the store queue is full; hot paths avoid
syncand uselwsyncor no barrier when only single-thread ordering is needed.
Related Instructions
isync— instruction-fetch barrier.eieio— lighter I/O barrier for caching-inhibited storage.lwsync— same encoding,L=1; not separately enumerated in this page set.
IBM Reference
- AIX 7.3 —
sync(Synchronize) - PowerISA v2.07B, Book II, §1.7 — defines
hwsync/lwsync/ptesyncsemantics.