Files
Sylpheed/tools/ppc-manual/alu/negx.md
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

5.5 KiB
Raw Permalink Blame History

negx — Negate

Category: Integer ALU · Form: XO · Opcode: 0x7c0000d0

Assembler Mnemonics

Mnemonic XML entry Flags Description
neg negx — Negate
nego negx OE=1 Negate
neg. negx Rc=1 Negate
nego. negx OE=1, Rc=1 Negate

Syntax

neg[OE][Rc] [RD], [RA]

Encoding

negx — form XO

  • Opcode word: 0x7c0000d0
  • Primary opcode (bits 0–5): 31
  • Extended opcode: 104
  • Synchronising: no
Bits Field Meaning
0–5 OPCD primary opcode (31)
6–10 RT destination GPR
11–15 RA source A
16–20 RB source B
21 OE overflow-enable flag
22–30 XO extended opcode (9 bits)
31 Rc record-form flag

Operands

Field Role Description
RA negx: read Source GPR (r0–r31).
RD negx: write Destination GPR.
CR negx: write (conditional) Condition-register update. When Rc=1, CR field 0 (or CR6 for vector compares, CR1 for FPU) is updated from the result.
OE negx: write (conditional) Overflow-enable bit. When 1, the instruction updates XER[OV] and stickies XER[SO] on signed overflow.

Register Effects

negx

  • Reads (always): RA
  • Reads (conditional): none
  • Writes (always): RD
  • Writes (conditional): CR, OE

Status-Register Effects

  • negx: CR0 ← signed-compare(result, 0) with SO ← XER[SO], when Rc=1.; XER[OV] ← signed-overflow(result); XER[SO] stickies, when OE=1.

Operation (pseudocode)

RT <- ~(RA) + 1

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

negx

Canary emitter (frozen snapshot @ f21ebd49e9)
int InstrEmit_negx(PPCHIRBuilder& f, const InstrData& i) {
  // RT <- ¬(RA) + 1
  if (i.XO.OE) {
    // Stub implementation.
    // TODO: Handle overflow flag for XER.
    // NOTE: 535507D4 (Raiden Fighters Aces) never seems to rely on this
    //   behavior, despite having OE set.
    Value* v = f.LoadGPR(i.XO.RA);
    if (v->AsUint64() == 0x8000000000000000) {
      f.StoreGPR(i.XO.RT, v);
      return 0;
    }
  }
  Value* v = f.Neg(f.LoadGPR(i.XO.RA));
  f.StoreGPR(i.XO.RT, v);
  if (i.XO.Rc) {
    f.UpdateCR(0, v);
  }
  return 0;
}

Special Cases & Edge Conditions

  • Two's-complement negate. RT ← ~RA + 1, equivalent to 0 − RA. A specialisation of subfx where RB is implicit zero.
  • INT64_MIN is its own negation. neg(0x8000000000000000) = 0x8000000000000000 — the only fixed point, and the canonical signed-overflow trigger for which nego should set XER[OV]. Canary never sets XER[OV]: its OE path only special-cases an operand that is literally 0x8000000000000000 (v->AsUint64()), storing it unchanged and skipping the CR update.
  • RB field unused. Set to 0 by assemblers; ignored.
  • Rc=1 CR0 update truncates to 32 bits in Canary (f.UpdateCR(0, v)). neg. of a 64-bit value whose high word decides the sign gives a CR0 that doesn't match spec, which compares the full 64-bit ~RA + 1 to zero.
  • No carry produced. Use subfic RT, RA, 0 (RT ← 0 − RA with carry) when you need the borrow.
  • Latency: single cycle. Negate is the cheapest XO-form ALU operation (cheaper than subf despite being a special case, because there's no RB operand fetch).
  • subfx — generalisation: neg RT, RA ≡ subf RT, RA, 0 (but the latter requires materialising 0 in a register).
  • subfic — RT ← SIMM − RA with XER[CA]; subfic RT, RA, 0 produces a borrow.
  • addx, addmex, addzex — for chained negation (multi-word two's complement).
  • not (simplified) — bit-wise complement via nor RA, RS, RS; distinct from negate.

IBM Reference