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

mark Int2Bytes(Int,Endianness,Signedness) rules as preserving definedness #4522

Merged

Conversation

jberthold
Copy link
Member

@jberthold jberthold commented Jul 15, 2024

Without the annotation, booster won't use these rules.
The /Int division is partial but harmless in these rules.

@rv-jenkins rv-jenkins changed the base branch from master to develop July 15, 2024 06:52
@jberthold jberthold force-pushed the HOTFIX-add-definedness-annotation-to-Int2Byte-conversions branch from cc2b63f to 84df943 Compare July 16, 2024 01:12
@jberthold jberthold marked this pull request as ready for review July 16, 2024 04:06
@rv-jenkins rv-jenkins merged commit 1721f7d into develop Jul 16, 2024
35 checks passed
@rv-jenkins rv-jenkins deleted the HOTFIX-add-definedness-annotation-to-Int2Byte-conversions branch July 16, 2024 06:02
rv-jenkins pushed a commit that referenced this pull request Jul 23, 2024
…for booster (#4533)

The previous change #4522 was insufficient to make the equations usable
in `booster`. Matches with literal `Int` constants will still be
indeterminate, so this PR removes the literals from the rule LHSs.

* Use `0 ==Int I` instead of a syntactic _match_ in the equation for
argument `0`. This enables evaluating terms with `I ==Int 0` in the path
condition.
* Remove equation with literal `-1` and widen requires in equation for
negative arguments (previously `I <Int -1`, now `I <Int 0`). The result
is the same as before with no extra equation required.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants