Brian DegenhardtandClaude Fable 5
71fdc2f03b
The instrumentation that localized SL-07, kept for the next hunt: eerunner stepdiff timer-taint classifier: - Bound the taint walk at the observation pc: the offending block can end mid-disasm (e.g. at an ei), and walking on into the NEXT block's jr delay slot let an untainted overwrite erase taint that was live at the observation point (a v0 timer read classified as a real divergence). - Seed the const-tracker with the interpreter's register file snapped at the offending block's entry (one extra frame re-run), so load addresses materialized in earlier blocks resolve - the software-virtual-clock accumulator shape (lui 0x1000 in one block, ori 0x800 in the next) was under-tainting. Every unmodeled GPR-writing op now clears known[] so a seeded value can never go stale into an over-taint. - Widen the benign class from the four EE timer COUNTs to cycle-phase MMIO (0x1000xxxx hardware regs + GS privileged bank): DMAC CHCR tag fields etc. legitimately read back a different transfer phase under JIT-vs- interp cycle granularity. The ResyncAfter reconvergence gate remains the safety net against masking real bugs. EE rec testing-only env knobs (no production effect when unset): - YAPS2_EESB: bitmask of continuation-site families (bit0 BEQ/BNE, bit1 BLEZ/BGTZ, bit2 REGIMM BLTZ/BGEZ; 0 = pre-superblock block formation). - YAPS2_EESB_LO/HI: guest-pc window for sites - the binary search over this window is what pinned SL-07 to one branch at 0x3f84c8. - YAPS2_EESB_DUMP=<hex pc>: disassemble any block covering that pc after finalize (needs INCLUDE_DISASSEMBLER; no-op otherwise). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
yaps2
This is a fork of PCSX2 targeting ARM based linux handheld devices. We're aiming to be performant and compatible on lower end ARM hardware, and adopt a "by any means" philosophy.
Thanks
A massive thank you to the PCSX2 team for 20 years of dedication. yaps2 doesn't meet the rigor required of PCSX2 upstream commits, but maybe someday it will.
The following people worked on the yaps2 fork of this project:
- bmdhacks
- tokyovigilante
- pstef
FAQ
Is it good?
A: Yeah. It's pretty fast.
Where do I get builds of this software?
A: Builds are available in nightly releases of Rocknix and Batocera
Did you vibe code it? I see that claude authors your commits you cheater!
A: This fork was written by seasoned developers using LLM devleopment tools. Our philosophy is focused on results, not policing methodology, and modern LLM tools are the most effective way for us to reach our goals.
Can I contribute?
A: Sure. Send a PR. If it's vibe-coded trash we'll reject it. If it's good we'll use it.
Can I fork this project for my own purposes?
A: Sure. If you do cool stuff we'll probably use your code.
Don't you know about XYZ project that already does this
A: Yes we probably copied a lot of their techniques.
Can I make feature requests or tell you that I don't like what you're doing or how you're doing it?
A: Look, we're not trying to be a serious project here so no.
Can I make bug reports?
A: Absolutely, file a github issue and we might look at it.