Files
sim f3c512f2ab 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

4.6 KiB
Raw Permalink Blame History

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 05): 31
  • Extended opcode: 598
  • 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

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 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 sync complete with respect to all other threads/processors before any subsequent memory access begins. Drains the store queue.
  • L field selects sync class. L=0 is full hwsync (the default). L=1 is lwsync — orders only loads-after-loads, loads-after-stores, and stores-after-stores (not stores-after-loads). The Xenon implements both via the same encoding with L (bit 9) selecting variant. Most disassembly shows the unsuffixed sync mnemonic, which assembles to L=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 uses lwsync after the load.
  • Canary emits f.MemoryBarrier(), as for eieio; isync is a plain f.Nop(). A sequential C translation needs neither: host program order subsumes the PPC ordering.
  • Distinct from isync, which orders the instruction stream — sync does not refetch instructions.
  • Slow on real hardware. Hundreds of cycles when the store queue is full; hot paths avoid sync and use lwsync or no barrier when only single-thread ordering is needed.
  • 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