Lars Brinkhoff
Lars Brinkhoff
I had a similar idea today. The overall concept is the same, I think. It depends on how you propose a chain being set up. My idea was to implement...
Maybe a terminating `NULL`, or a nicely named `end_sequence`.
Agreed. I edited the example. Possibly, `ea_begin_modify` should only handle memory destination operands, and let the instruction handle register destination operands.
I have something that's almost working now. I don't think there will be any problem aborting an instruction midway. Just `ujump` somewhere else, or call `u_start_sequence`. I don't know exactly...
For that matter, do you have a handle on externally versus internally generated bus errors?
I read something in the 68000 User's Manual, but now that I read it again, I see it can be interpreted another way: > An address error is similar to...
Well, it says "similar" to a bus error. It doesn't say it's done identically. But of course, it's slightly easier to implement them identically.
It looks like it might be possible to implement the hardware algorithm, and thus compute the result in parallel with the cycle time. It would be a good fit for...
The Yacht table also seems to have some algorithm for calculating the number of `DIVU` and `DIVS` cycles.
Isn't this the map originally made by Steven Roy? See here: http://dungeonsndigressions.blogspot.com/2009/05/steven-roys-beauty-of-map.html It wasn't drawn by the original Zork people.