forked from Z3Prover/z3
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Length based conversion encoding of int conversions #121
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jurajsic
force-pushed
the
to-from-int-length-based
branch
from
February 21, 2024 14:04
a73ee4d
to
517657f
Compare
jurajsic
force-pushed
the
to-from-int-length-based
branch
from
February 25, 2024 17:37
f0202c4
to
bdc5b2c
Compare
jurajsic
changed the title
int conversions are handled in more concise way
Length based conversion encoding of int conversions
Feb 25, 2024
Preliminary results (without
|
Comparison with current
|
vhavlena
approved these changes
Feb 26, 2024
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.
Nice work! I am happy with the optimizations. Just a few comments.
jurajsic
commented
Feb 26, 2024
@vhavlena can I merge it? |
Yes, sure |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Instead of creating each case while creating LIA formula encoding int conversions, we now handle them by legnths, so for example if we have
i = to_int(s_1 s_2)
withs_1 \in [4-8][0-9][0-9]
ands_2 \in [2-3][5-9]
instead of putting
i = 40025 || i = 40026 || ....
we now create400 <= s_1^i <= 899
,25 <= s_2^i <= 29 || 35 <= s_2^i <= 39
andi = s_1^i*100 + s_2^i
.