This repository has been archived by the owner on Jun 9, 2021. It is now read-only.
Do the right thing when encountering 0-width bitvectors in the What4 backend #196
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
|
As of GaloisInc/saw-script#1179, saw-script is now using an up-to-date version of saw-core, so hopefully nothing else is blocking a downstream PR anymore. |
…backend. Fixes the root cause of GaloisInc/saw-script#872
robdockins
force-pushed
the
what4-zerobv
branch
from
20bdf3a
to
e4c5954
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes the root cause of GaloisInc/saw-script#872
I haven't made an downstream PR in saw-script yet, as this seems blocked up on some other stuff merging first.