-
Notifications
You must be signed in to change notification settings - Fork 77
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
Autotuning of Configuration #772
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution!
Given that you've touched the SV-COMP files here already, I suppose you've already tried this on sv-benchmarks? If so, then does this already show some improvement there?
I am testing with the sv-comp tests and there are some improvements. |
Active if the loop uses malloc/threads/locks Moved the creation of the CFG to seperate file to break dependency cycle
Comment cleanup
fixed handling of __builtin functions when setting congruence attributes
rename to autotune find malloc wrappers
by variable, type attributes Small fixes to loopheuristic
loop unrolling now seperately activateable over ana.autotune.activated
small fixes annotationg variables for tracking with apron choosing options annotate arrays
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be good to have complete SV-COMP before vs after runs with this to see how well this ad-hoc stuff works.
tests/regression/58-array_annotations/01-var_array_annotation.c
Outdated
Show resolved
Hide resolved
tests/regression/58-array_annotations/03-change_domain_array_annotation.c
Outdated
Show resolved
Hide resolved
Co-authored-by: Simmo Saan <simmo.saan@gmail.com>
I did this in my bachelor's thesis: pages 19 and 20 contain tables with the results of the different features and some further configurations. In the text surrounding it I describe a bit further what changed. |
Changes for pull request
Besides the couple of unresolved comments, the test group 58-array_annotations needs to be renumbered to 60-array_annotations to avoid conflict on master. |
@sim642 Any more comments here or are we good to merge? |
CHANGES: Functionally equivalent to Goblint in SV-COMP 2023. * Add automatic configuration tuning (goblint/analyzer#772). * Add many library function specifications (goblint/analyzer#865, goblint/analyzer#868, goblint/analyzer#878, goblint/analyzer#884, goblint/analyzer#886). * Reorganize library stubs (goblint/analyzer#814, goblint/analyzer#845). * Add Trace Event Format output to timing (goblint/analyzer#844). * Optimize domains for address and path sets (goblint/analyzer#803, goblint/analyzer#809).
Adds an option that tries choosing some configurations automatically based on the file that is analyzed.
Already implemented:
This is part of my bachelor thesis and still work in progress.