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.
Now PHP tracing JIT may lose some parts of the "hot" code.
In case we have a root LOOP trace with an inlined call of some function, and we get a SIDE exit inside that function - we start recording a side trace, but we finish recording at the RETURN of the inlined function. As result the opcodes between RETURN from SIDE trace and root trace LOOP exit might be never traced and were always executed in interpreter.
This patch introduces a "ret_depth" argument that prevents stopping tracing on RETURN of such SIDE trace.
This is targeted to PHP-8.4, because this may disclose unrelated JIT problems and I don't like to do this in old stable releases.