Do not normalize bounds for invalid decls#1090
Merged
Merged
Conversation
sulekhark
reviewed
Jun 10, 2021
sulekhark
left a comment
Contributor
There was a problem hiding this comment.
LGTM!
Do we want to remove the function Sema::ExpandBoundsToRange by fusing it with Sema::NormalizeBounds (with a check to avoid unnecessary expansion if already expanded)? This is because both NormalizeBounds and ExpandBoundsToRange can potentially be called from outside the class, and ExpandBoundsToRange does not have the same check for an invalid decl. Moreover, currently ExpandBoundsToRange is called only by NormalizeBounds. It does not make sense to add another check for invalid decl in ExpandBoundsToRange.
|
LGTM. Thanks. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #1084
This PR fixes a crash that would occur in
Sema::NormalizeBoundsfor certain kinds of (invalid)VarDecls. When expanding bounds to a range,Semaneeds to create aDeclRefExprfor aVarDecl. In order to do so, it may callSema::ConvertToFullyCheckedType, which asserts that the type of theVarDeclis not an unchecked type and does not contain an unchecked type.Consider the following example:
In a checked scope, this produces the error "parameter in a checked scope must have a bounds-safe interface type that uses only checked types or parameter/return types with bounds-safe interfaces".
pis an invalid declaration.Accounting for the bounds-safe interface, the type of
pis_Array_ptr<int *>. If we attempt to normalize the declared boundscount(i)forp, the assertion inConvertToFullyCheckedTypefails since_Array_ptr<int *>contains the unchecked typeint *. Therefore, we should not attempt to normalize the declared bounds forp. We do not includepin the observed bounds context, and we do not attempt to validate the bounds ofpafter each statement. The statementi = 0results in no bounds validation errors.