I'm an interested party, but due to lack of time and skill I don't think I could be a meaningful contributor - sorry.

I had a quick look at the sources for VICE2.1, and I see a lot of attention to cycle-accurate detail. Even arranging to ignore that is going to take some effort. The file src/drive/drivecpu.c does a #include of src/6510core.c - I think the solution will touch one or both of those two, and can perhaps be limited to touching those two files.

Sorry
Ed

ps. source links are to the viceplus project, since merged back into vice, but which has linkable sources.

As one of the (older, ex-) authors of vice...



The file 6510core.c is not only included in the drivecpu.c, but also in the maincpu.c files. It (6510core.c) is the definition of a cycle-exact 6502 - the actual code is generated in the *cpu.c files - as VICE emulates a number of CPUs in its different binaries: C64 main cpu, C128 main 6510 CPU, PET main cpu, VIC20 main cpu, CBM II main cpu, and as you mentioned in the drive emulation (IIRC one cpu file for the 15x1 and one cpu file for the PET dual drives, but I could be mistaken here)

The *cpu.c files add the computer-specific stuff around the 6502 core.

So if you change 6510core.c, you most probably need to modify all the others in VICE.

I'd rather put the 65816 core in a separate file, with a different main cpu file, and keep the working code untouched, except for the switch "use SuperCPU" which would jump into the new (65816) main cpu code.

André

Oops - thanks for the extra detail and the guidance. My quick scan of the code was inadequate!

Cheers
Ed

THIS IS ALL YOUR FAULT! ALL YOUR FAULT!

Thanks for the feedback. My initial reading of the code also was inadequate.