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.5 KiB
Raw Permalink Blame History

orcx — OR with Complement

Category: Integer ALU · Form: X · Opcode: 0x7c000338

Assembler Mnemonics

Mnemonic XML entry Flags Description
orc orcx OR with Complement
orc. orcx Rc=1 OR with Complement

Syntax

orc[Rc] [RA], [RS], [RB]

Encoding

orcx — form X

  • Opcode word: 0x7c000338
  • Primary opcode (bits 05): 31
  • Extended opcode: 412
  • 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
RS orcx: read Source GPR (alias for RD in some stores).
RB orcx: read Source GPR.
RA orcx: write Source GPR (r0r31).
CR orcx: write (conditional) Condition-register update. When Rc=1, CR field 0 (or CR6 for vector compares, CR1 for FPU) is updated from the result.

Register Effects

orcx

  • Reads (always): RS, RB
  • Reads (conditional): none
  • Writes (always): RA
  • Writes (conditional): CR

Status-Register Effects

  • orcx: CR0 ← signed-compare(result, 0) with SO ← XER[SO], when Rc=1.

Operation (pseudocode)

RA <- (RS) | ~(RB)

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

orcx

Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_orcx(PPCHIRBuilder& f, const InstrData& i) {
  // RA <- (RS) | ¬(RB)
  Value* ra = f.Or(f.LoadGPR(i.X.RT), f.Not(f.LoadGPR(i.X.RB)));
  f.StoreGPR(i.X.RA, ra);
  if (i.X.Rc) {
    f.UpdateCR(0, ra);
  }
  return 0;
}

Special Cases & Edge Conditions

  • RA ← RS OR (NOT RB). The complement is on RB. Useful for setting bits outside a mask — e.g. orc r3, r3, r4 sets in r3 every bit not set in r4.
  • Idiom: orc RA, RS, RS = RS | ~RS = -1 (all ones). Cheaper-looking than constructing 1 via lis+ori, but the assembler usually prefers li RA, -1 or eqv RA, RS, RS.
  • Operand convention is X-form (RA destination, RS/RB sources).
  • 64-bit operation on Xenon; Canary emits a full-width f.Or(RS, f.Not(RB)).
  • No OE or XER side effects.
  • Rc=1 CR0 update truncates to 32 bits in Canary (f.UpdateCR(0, v)). Because ~RB typically has high bits set, orc. results whose low word's sign differs from the full word's give different CR0 in spec and Canary.
  • orx — base OR (no complement).
  • andcx — AND-with-complement; sister c form.
  • norx, nandx — full-result complements.
  • eqvx~(RS XOR RB).

IBM Reference