Repository navigation
Hardware Oddity RCC Boundaries
Evidence: NVIDIA vertex-program specification, not yet an Xbox bitwise measurement. The NV_vertex_program1_1 specification defines RCC as a clamped reciprocal, not merely 1/x. It bounds signed magnitudes between 2^-64 and 2^64, including signed-zero behavior.
| Input | Specified RCC result |
|---|---|
| +0 | +2^64 |
| -0 | -2^64 |
| +infinity | +2^-64 |
| -infinity | -2^-64 |
The binary32 boundary words are 0x5F800000 and 0x1F800000, with sign-bit counterparts. Use these bits rather than rounded decimal approximations.
Proposed test: compare exact input/output words for signed zeros, infinities, subnormals, NaNs, and adjacent representable values on NV2A. Record exception behavior independently of ordinary finite reciprocal quality.
See also NV2A Graphics Architecture.
DSP tooling guide and navigation updated November 2, 2026 for experimental PR #384, source 8f51d237. Capture/replay usage and limits.
The earlier wiki-wide review was published November 1, 2026. Emulator source: b7140848. Reviewed wiki content: 1d2b671. Current status · Release availability · Publication process.
- Home
- Current status
- Stable versus main
- Implemented mechanisms
- Controls and defaults
- Measured results and limits
- Complete change register
- System
- CPU and vCPU
- Memory and DMA
- Graphics / NV2A
- APU and audio
- Timing and timers
- Platform and I/O
- Hardware observations
- Fidelity boundaries
- Methodology
- PGR2 routes
- Debugging lag / hot paths
- Tools and commands
- DSP capture, replay and fuzzing
- HLE readiness and public XISO proof
- Concurrent DSP shadow and OpenAL proof
- DSP HLE operation inventory
- DSP HLE fix examples and testing
- Development
- Upstream shortlist
- Wiki maintenance
- Research / retired work
- Optimization catalog
- Hot-path shortcuts
- Researched experiments
- Unproven proposal directory
- PR lessons
- September26 snapshot
Repository · PRs · Issues