6502/CLK
1
0
Fork 0
mirror of https://github.com/TomHarte/CLK.git synced 2024-11-26 23:52:26 +00:00
Code Issues Projects Releases Wiki Activity

Work further to guess at caller's intention for set_state.

Browse Source 
Probably I should just eliminate the initial reset, somehow.
This commit is contained in:
Thomas Harte 2022-05-25 17:01:18 -04:00
parent 68b184885f
commit 64491525b4
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
OSBindings/Mac/Clock SignalTests/TestRunner68000.hpp
View File

@ -55,11 +55,13 @@ class RAM68000: public CPU::MC68000Mk2::BusHandler {
void will_perform(uint32_t, uint16_t) {
if(!has_run_) {
// Patch back in the status result, since reset will
// have affected that.
auto state = m68000_.get_state();
state.registers.status = initial_state_.registers.status;
m68000_.set_state(state);
// Reapply all of initial state except the program counter and stack pointers.
// Also copy the supervisor stack pointer to the user.
const auto state = m68000_.get_state();
initial_state_.registers.program_counter = state.registers.program_counter;
initial_state_.registers.user_stack_pointer = state.registers.supervisor_stack_pointer;
initial_state_.registers.supervisor_stack_pointer = state.registers.supervisor_stack_pointer;
m68000_.set_state(initial_state_);
}
--instructions_remaining_;