Fix SInt literals to reject too small of widths (backport #4786) #4788
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.
Found by @tymcauley ucb-bar/fixedpoint#11 (comment)
This bug was introduced 2 years ago when we added support for zero-width literals: #2932
The problem is that
BigInt.bitlengthexcludes the sign bit, so we need to add 1 to it for SInts (which is what we originally did), BUT we need special case support for zero-width SInts (only when specified).Contributor Checklist
docs/src?Type of Improvement
Desired Merge Strategy
Release Notes
For users attempting to reinterpret raw 2s complement values as SInts, use
.U.asSInt.Reviewer Checklist (only modified by reviewer)
3.6.x,5.x, or6.xdepending on impact, API modification or big change:7.0)?Enable auto-merge (squash)and clean up the commit message.Create a merge commit.This is an automatic backport of pull request #4786 done by [Mergify](https://mergify.com).