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

Measure the cost of per-instruction callback in bxcpu #141

Open
0vercl0k opened this issue Nov 13, 2022 · 0 comments
Open

Measure the cost of per-instruction callback in bxcpu #141

0vercl0k opened this issue Nov 13, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@0vercl0k
Copy link
Owner

In #137, edge-coverage is implemented by using a set of hooks that executes on branches vs after every instruction. This means that potentially, we could stop using the per-instruction hook when fuzzing and potentially get a good performance win.

This task is about trying to find out how much of a speed-up this would bring, and if it looks decent to make edge coverage default, use per-instruction hook when tracing and implement a breakpoint mechanism that doesn't rely on the per-instruction hook.

@0vercl0k 0vercl0k added the enhancement New feature or request label Nov 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant