How did that "secret" tick in the M6502 implementation get there???

This commit is contained in:
Adrian Conlon 2024-01-06 20:53:50 +00:00
parent 9334f6ee93
commit 69a845e2f4
2 changed files with 1 additions and 2 deletions

View File

@ -84,7 +84,7 @@ public:
[[nodiscard]] constexpr auto cycles() const noexcept { return m_cycles; }
[[nodiscard]] constexpr auto valid() const noexcept { return m_valid; }
[[nodiscard]] constexpr auto invalid() const noexcept { return !valid(); }
[[nodiscard]] constexpr auto unimplemented() const noexcept { return invalid() && m_cycle_count_mismatch && (cycles() == 1); }
[[nodiscard]] constexpr auto unimplemented() const noexcept { return invalid() && m_cycle_count_mismatch && (cycles() == 0); }
[[nodiscard]] constexpr auto implemented() const noexcept { return !unimplemented(); }
[[nodiscard]] constexpr const auto& messages() const noexcept { return m_messages; }

View File

@ -24,7 +24,6 @@ int EightBit::MOS6502::step() noexcept {
resetCycles();
ExecutingInstruction.fire(*this);
if (LIKELY(powered())) {
tick();
if (UNLIKELY(lowered(SO())))
handleSO();
if (LIKELY(raised(RDY()))) {