Conversation
Member
There was a problem hiding this comment.
This is just a warning, we don't need a blurb.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
instruction_funcptr_tracing_tableis only used byENTER_TRACING()andIS_JIT_TRACING(), and those use it only when_Py_TIER2is set. Without the JIT the table is never referenced, so GCC warns. The computed goto version,opcode_tracing_targets_table, is already guarded by#if _Py_TIER2. This adds the same guard to the tail calling table in the generator and regenerates the headers.Fixes #158795
instruction_funcptr_tracing_tabledefined but not used with--with-tail-call-interp#158795