[bug][slang] Fix case selector huge bitwidth segmentation fault #1217
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.
Hi @MikePopoloski!
There are a two examples of
casex
which works incorrect with slang:and
I think the whole point is that it is dangerous to use
unions
(for example - here), especially since it is impossible to check which type was actually written to the tree node. This can also happen because of different bit lengths of labels (in one case - for the first labelvalue.getBitWidth()
returns 12 (leading zeros in front), and in the other 101).