Error on excessively large control flow graphs #18246
Merged
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.
This PR improves our handling of excessively large control flow graphs: If control flow analysis leads to a stack depth of 2500 recursive calls, we now issue an error and disable control flow analysis for the remainder of the containing function or module body. Previously we'd simply overflow the call stack.
The 2500 recursive call limit was experimentally determined. Control flow patterns that cause recursion in the control flow analyzer (such as #11432) overflow the stack somewhere between 2500 and 5000 calls.
No RWC tests are affected by this change.
Fixes #14314 in the sense that it doesn't overflow the stack. However, #14314 still takes >80s to compile.