Lofty

Well, I'm looking for the `.json` file generated by Yosys, the `.qsf` file and the nextpnr-mistral command line

I found and fixed the issue last night, and then promptly spent the day sleeping. Anyway, the issue should be fixed, and it compiles on my end with latest nextpnr.

Unfortunately PLLs aren't plumbed into nextpnr, since the vendor primitive is an *utter mess* and I have the irrational hope I can do better than it...

The PS2 BIOS contains a mysterious area located around `1a000000-1a00000f`, alongside some other areas.

I think it's worth chipping in with the approach I have in mind for ocps2, which is very much in its infancy, but I have pages of plans for how...

They'll basically always be predicted correctly, because if they are ever true then the JIT will just emit more careful code.

I sent some PS2 boards over to @whitequark; she's offered to decap and delayer them, so we can reverse engineer from the die shots of things like the MECHACON.

Fuzzing is difficult because it's not always obvious what internal affects it has. I think dumping the ROM is a better approach. We have service manuals for the 39k series,...

I think the current code tries to recognise division operations by pattern matching, so that's something we could/should work on.

Something @skmp mentioned is letting the frontends have higher-level concepts like function entries and exits, and then put them to a lowering pass to SHIL. This would look something like...