Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clean-ups & picosim hardware breakpoint support #482

Merged
merged 5 commits into from
Dec 14, 2024

Conversation

sneakywumpus
Copy link
Contributor

@sneakywumpus sneakywumpus commented Dec 14, 2024

Guard FAST_BLOCK by !EXCLUDE_Z80.
Remove unneeded checks from simdefs.h (already guarded in sim.h).

simice: clean-up optional features messages.

Add hardware breakpoint support to picosim, so we can test performance impact.

Or we could switch from the "See what you are missing" paradigm and remove the not enabled commands entirely from the ICE. Thoughts?

Guard FAST_BLOCK by !EXCLUDE_Z80.
Remove unneeded checks from simdefs.h (already guarded in sim.h)
So we can test performance impact.
@sneakywumpus sneakywumpus changed the title clean-ups clean-ups & picosim hardware breakpoint support Dec 14, 2024
Also check for '\0' for 'b' and 'bh'.
Don't mix f* stdio calls with non-f*.
@udo-munk
Copy link
Owner

The see what you are missing commands were there for those not familiar with the system. One could remove them completely, but others will not get aware anymore that there are more compile time options.

@udo-munk udo-munk merged commit 6f7aaa8 into udo-munk:dev Dec 14, 2024
@sneakywumpus
Copy link
Contributor Author

Ok, I'll leave it as it is.

Does my implementation of the hardware breakpoint do what you would expect? I've zero experience with real hardware ICE... If yes, I would add it to the rest of the simulators.

@udo-munk
Copy link
Owner

Yes, works well and is like the implementation in a real hardware ICE from what I can remember.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants