[HWToBTOR2] Use APInt value directly in constant generation #7853
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.
Currently creating a constant with any value that won't fit in an i64 will break HWToBTOR2 as it tries to fetch the value from an APInt and place it in an int64_t - not ideal if you have wires wider than 64 bits.
Breaking example:
This just swaps to using the APInt directly to print the value - AFAICT this will still yield correct BTOR2.