Files
Sylpheed/tools/ppc-manual/control/crorc.md
sim 84856fc081
All checks were successful
CI / Native — linux (pull_request) Successful in 2h1m57s
CI / WASM — Web (pull_request) Successful in 28m8s
CI / Formatting (pull_request) Successful in 1m26s
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

5.1 KiB
Raw Blame History

crorc — Condition Register OR with Complement

Category: Control / CR / SPR · Form: XL · Opcode: 0x4c000342

Assembler Mnemonics

Mnemonic XML entry Flags Description
crorc crorc Condition Register OR with Complement

Syntax

crorc [CRBD], [CRBA], [CRBB]

Encoding

crorc — form XL

  • Opcode word: 0x4c000342
  • Primary opcode (bits 05): 19
  • Extended opcode: 417
  • Synchronising: no
Bits Field Meaning
05 OPCD primary opcode (19)
610 BT/BO target / branch options
1115 BA/BI source A / CR bit to test
1620 BB source B
2130 XO extended opcode (10 bits)
31 LK link flag

Operands

Field Role Description
CRBA crorc: read CR source bit A (031).
CRBB crorc: read CR source bit B (031).
CRBD crorc: write CR destination bit (031).

Register Effects

crorc

  • Reads (always): CRBA, CRBB
  • Reads (conditional): none
  • Writes (always): CRBD
  • 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

crorc

Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_crorc(PPCHIRBuilder& f, const InstrData& i) {
  // CR[bt] <- CR[ba] | ¬CR[bb]   bt=bo, ba=bi, bb=bb
  Value* ba = f.LoadCRField(i.XL.BI >> 2, i.XL.BI & 3);
  Value* bb = f.LoadCRField(i.XL.BB >> 2, i.XL.BB & 3);
  Value* bt = f.Or(ba, f.And(f.Not(bb), f.LoadConstantInt8(0x01)));
  f.StoreCRField(i.XL.BO >> 2, i.XL.BO & 3, bt);
  return 0;
}

Special Cases & Edge Conditions

  • Operation. CR[CRBD] ← CR[CRBA] OR ¬CR[CRBB] — a one-instruction "A or not B" implication. Result is 0 only when A=0 and B=1.
  • Logical implication. B → A¬B A, which is exactly crorc BT, BA, BB. Useful for predicates of the form "if B holds, then A must hold".
  • Identity case. crorc BT, BA, BA always yields 1 (A ¬A), an alternative to creqv for setting a bit.
  • Bit-level operands. 5-bit absolute CR-bit indices; sources and destination may all be in different CR fields.
  • Use case. Compose "if B then A" guards without a separate complement step.
  • No Rc / OE. Doesn't update CR0 or XER.
  • Not synchronising. Reorderable.
  • Canary status. Canary emits OR-with-NOT directly.

crorc has no dedicated simplified mnemonic. See cror for crmove.

IBM Reference