GH-94841: Fix usage of Py_ALWAYS_INLINE#104409
Merged
brandtbucher merged 1 commit intopython:mainfrom May 12, 2023
Merged
Conversation
Member
Author
Contributor
|
Thanks @brandtbucher for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11. |
Contributor
|
Sorry, @brandtbucher, I could not cleanly backport this to |
brandtbucher
added a commit
to brandtbucher/cpython
that referenced
this pull request
May 12, 2023
(cherry picked from commit a10b026) Co-authored-by: Brandt Bucher <brandtbucher@microsoft.com>
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
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 silences a compiler warning on non-debug builds:
The issue is that
Py_ALWAYS_INLINEonly works forstatic inlinefunctions.I'm also going to run the benchmarks on this out of an abundance of caution, since (at least in theory) this could force the compiler to make poor inlining decisions it currently avoids.