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

Feature: Collecting solving statistics for diagonstics #534

Open
ThomasHaas opened this issue Oct 14, 2023 · 0 comments
Open

Feature: Collecting solving statistics for diagonstics #534

ThomasHaas opened this issue Oct 14, 2023 · 0 comments

Comments

@ThomasHaas
Copy link
Collaborator

ThomasHaas commented Oct 14, 2023

We should have a (toggable) feature in the Refinement procedure that allows us to collect (dynamic) information about all observed executions and check that against our statically derived information. This would allow us to more easily find weak spots and/or places for optimizations.

We should collect at least:

  • The events that were executed (+ frequency maybe?). Never-executed events show a possibility to improve dead code elimination.
  • The addresses/aliases of memory events. We can check the dynamic aliases against our alias analysis to see how (in)accurate we are and maybe get ideas to improve the analysis.
  • The values of memory events and local events. The values are helpful to understand if we could reduce the width of bitvectors (i.e., if a value-range analysis would be good to have).
  • The edges of base relations like co and rf. This could show weaknesses in our relation analysis.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant