Optimize order of provers to reduce proof time #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use of the tool SPAT showed that a lot of time was spend by CVC4 on some VC
that Z3 could prove easily. Changing the order was not a home run though, as
Z3 runs a long time on some VC in sparknack-utils.adb. Solution is to
special-case this unit to run the provers in the other order. On my laptop,
running time goes from 1 mn 50 s to 1 mn 3 s.