Reject loop candidates that contain catch blocks #23188
Open
+21
−0
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.
Reject natural loops as idiom candidates if any catch handler block appears in the loop region (including nested blocks). Loops containing catch blocks are not suitable for CISC idiom transformations (e.g., MemSet/MemCpy) because the exception path alters the loop region’s CFG and prevents extraction/alignment of the required idiom region. This change avoids wasted idiom analysis on loops whose CFG contains exception-handler paths.
Related: #21417