post-opt: taint :consistent when statement may raise inconsistently #54219
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.
When an inconsistent statement doesn’t affect the return value, post-opt analysis will try to refine it to
:consistent
. However this refinement is invalid if the statement could throw, as:consistent
requires consistent termination.For the time being, this commit implements the most conservative fix. There might be a need to analyze
:nothrow
in a data-flow sensitive way in the post-opt analysis as like we do for:consistent
.