Description[turbofan] Properly respect --max_inlining_levels with Ignition.
The logic to test whether we already reached --max_inlining_levels
when inlining into some optimized function only checked specifically
for FrameStateType::kJavaScriptFunction, and thereby didn't properly
account for FrameStateType::kInterpretedFunction, which is what we
see when we come in via the bytecode pipeline.
Committed: https://crrev.com/a5ca412e5acb8c2dffcc4ddeff74d3132064c29b
Cr-Commit-Position: refs/heads/master@{#39328}
Patch Set 1 #
Dependent Patchsets: Messages
Total messages: 12 (7 generated)
|