Files
Sylpheed/tools/ppc-manual/alu/ori.md
MechaCat02 6bdbf89ebc
All checks were successful
CI / Native — linux (pull_request) Successful in 37m56s
CI / WASM — Web (pull_request) Successful in 28m5s
CI / Formatting (pull_request) Successful in 59s
chore(tools): adopt the PPC manual and a canary launcher that works anywhere
CONSOLIDATION.md Phase 6. Both lived untracked in the project root -- on one
disk, backed up by nothing.

  tools/ppc-manual/   393 files, 3.7 MB. 455 instructions, 350 family pages,
                      598 mnemonics resolvable through index.json, plus the
                      generator that produced them.
  tools/run-canary.sh the oracle launcher.

🔴 THE LAUNCHER WAS BROKEN IN TWO WAYS AND IS REWRITTEN, not copied:

  * it pointed at `xenia-rs/sylpheed.iso`, a SYMLINK. Wine cannot resolve one
    and says "path invalid", which reads as a corrupt image rather than a path
    problem -- it has cost a session before. It now points at the real file and
    warns if handed a symlink.
  * it hardcoded one machine's absolute paths, and named `xenia-rs`, which this
    consolidation retires. Now derived from the script's own location, with
    SYLPH_CANARY_BIN / SYLPH_ISO overrides and a check that each exists.

The standing constraints are in its header where someone will read them: one
emulator at a time, Canary runs MUTED, and never judge a crash or a hang from
a Bash-launched run -- a SIGKILL that looked like the binary was the editor's
process supervisor.

⚠️ The manual's GENERATOR reads the xenia-rs source tree, which is going away.
Its decoder now lives here as crates/sylpheed-ppc, so the generator must be
repointed before it is run again. Recorded in the README rather than left for
someone to discover; the manual's content is checked in and regenerates from
nothing implicitly.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-13 21:18:00 +02:00

4.3 KiB
Raw Blame History

ori — OR Immediate

Category: Integer ALU · Form: D · Opcode: 0x60000000

Assembler Mnemonics

Mnemonic XML entry Flags Description
ori ori OR Immediate

Syntax

ori [RA], [RS], [UIMM]

Encoding

ori — form D

  • Opcode word: 0x60000000
  • Primary opcode (bits 05): 24
  • Extended opcode:
  • Synchronising: no
Bits Field Meaning
05 OPCD primary opcode
610 RT destination GPR (or RS when storing)
1115 RA source GPR (0 ⇒ literal 0 for RA0 forms)
1631 D/SI/UI 16-bit signed or unsigned immediate

Operands

Field Role Description
RS ori: read Source GPR (alias for RD in some stores).
UIMM ori: read 16-bit unsigned immediate. Zero-extended.
RA ori: write Source GPR (r0r31).

Register Effects

ori

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

Status-Register Effects

No condition-register or status-register effects.

Operation (pseudocode)

RA <- (RS) | (0x0000 || UIMM)

C Translation Example

/* C translation: the xenia-rs interpreter arm below in           */
/* Implementation References is the authoritative semantic        */
/* snapshot. Translate it line-by-line:                            */
/*   - ctx.gpr[N]  -> r[N]       (or f[]/v[] for FPRs/VRs)        */
/*   - mem.read_u*/write_u* -> mem_read_u*_be / mem_write_u*_be   */
/*   - ctx.update_cr_signed(fld, v) -> update_cr_signed(fld, v)   */
/*   - ctx.xer_ca / xer_ov / xer_so -> xer.CA / xer.OV / xer.SO   */
/* The Register Effects and Status-Register Effects tables above  */
/* enumerate every side effect a faithful translation must emit.  */

Implementation References

ori

xenia-rs interpreter body (frozen snapshot)
        PpcOpcode::ori => {
            ctx.gpr[instr.ra()] = ctx.gpr[instr.rs()] | (instr.uimm16() as u64);
            ctx.pc += 4;
        }

Special Cases & Edge Conditions

  • No record form. Unlike andix, ori does not update CR0 — there is no ori.. If you need a CR update after OR-immediate, follow it with cmpwi or use orx with Rc=1.
  • Immediate is zero-extended. Only the low 16 bits of RA can be affected; the high 48 bits are passed through from RS unchanged.
  • ori 0, 0, 0 is the canonical NOP. All PowerPC NOPs assemble to this encoding (0x60000000). Disassemblers usually display this as nop.
  • Common idiom: build a 32-bit constant via lis + ori. lis r3, hi16; ori r3, r3, lo16 materialises any 32-bit immediate with no CR or XER disturbance.
  • 64-bit operation in xenia-rs. interpreter.rs:330 — full u64 OR; high bits unchanged from RS.
  • RA = 0 reads r0 (not the literal zero). Different from addi's RA0 semantics; ori uses the regular RA interpretation.
  • oris — same op with the immediate shifted left 16.
  • orx — register-register; supports Rc=1.
  • xori, xoris, andix, andisx — sister immediate logicals.
  • nop (simplified) — ori 0, 0, 0.

IBM Reference