Repository navigation
graphics: complete GPU milestones M9-M16 - #767
Conversation
f5d26ce to
226a785
Compare
Activate the production Newport resident path and explicit frontend modes. Complete IMPACT engine fidelity and snapshot lifecycle, make VPro GPU failures fail closed with full Octane snapshots, and add complete GR2 lifecycle state plus measured resident-GPU decision telemetry. Keep VPro bit-exact on Vulkan and D3D12, and retain gr2-jit after the evidence gate does not justify a resident RE3 wgpu implementation.
226a785 to
786a730
Compare
Performance contextWe do not currently have a committed plot, but the application-level acceptance data is sufficient to show the measured improvement over the ordinary CPU raster/JIT path. The comparison used the same installed IRIX 6.5 IP22 system and isolated overlays for CPU raster/JIT, Vulkan resident direct, and D3D12 resident direct. Atlantis ran after a 15-second warm-up for a 30-second measured interval on an RTX 5070 host with 16 logical CPUs.
Both GPU samples required This should be read as a live Newport/REX3 graphics-command throughput result, not a claim of 1.24-1.42x total emulator or guest-application FPS. IMPACT and VPro have separate workload/replay measurements, while GR2 retained Committed details: |
Important
#757 and #758 are integrated. This PR is rebased directly onto upstream
mainateb82d0aeand contains exactly one M9-M16 commit.Summary
gr2-jitafter the predefined resident-GPU gate produced an evidence-based no-goMilestones
M9+M10 - Newport production activation and frontends
M11+M12 - IMPACT correctness, residency, and lifecycle
gr4-jitM13+M14 - VPro residency and Octane snapshots
M15+M16 - GR2 lifecycle and measured GPU decision
state,vram, andzbufparts while retaining schema 6-9 decodinggr2-jitat 178-568 Mpx/s across 4-1,280-pixel spans, 1.33-2.86x faster than the interpreterDecision: defer a resident RE3 wgpu implementation and retain
gr2-jit. The traces establish batching potential, but there is no GPU prototype that beats the warm-JIT large-span baseline or proves the <=5% short-span bound; ordinary presentation still scans 1,310,720 host pixels per frame, and no repeatable representative guest benefit has been measured. This does not conclude that efficient acceleration is impossible.Commit scope
The incremental M9-M16 change is one commit (
786a7306), touching 95 files with 7,016 insertions and 956 deletions. GitHub now displays only this isolated commit.Validation
Current rebased tip on
mainateb82d0ae:cargo checkfor the combinedwgpu,gpujitcore configuration passediris-guiwithiris/wgpupassedgit diff --checkpassedFull consolidated-campaign validation:
gr4-jit: 227 active tests passed; two ignoredOne existing-checkout caveat: the tracked VPro golden fixture was checked out as CRLF despite
eol=lf, so the default byte-string comparison reported line-ending differences locally. The tolerance verifier reported zero moved rows and zero numeric differences in every field. A normalized checkout uses the tracked LF form; no broad fixture rewrite is included.