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.
bpo-46841: Use inline caching for attribute accesses #31640
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bpo-46841: Use inline caching for attribute accesses #31640
Changes from all commits
c2b0713
2d5e15a
5b06d97
828540a
4a6632c
2b876f1
097fdaf
4c71c12
09fbac5
e5229ce
452c78c
948a206
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given that
LOAD_METHOD_MODULE
andLOAD_ATTR_MODULE
share code, maybe change this to:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd rather leave it as-is. Otherwise, accessing the
attr
methods, including thecounter
, is a bit awkward.In response to your other comments: I don't think we're doing anything illegal here, since we only use one consistent cache layout for each specialized form (meaning,
_PyLoadMethodCache
and_AttrCache
members never alias each other). The exception is thecounter
member for all instructions, but C guarantees that it the first member of a struct will always be at offset0
. So no issues there.Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The existence of the
LOAD_MODULE_ATTR_OR_METHOD
macro implies that theLOAD_ATTR
andLOAD_METHOD
caches should have the same layout. Yet, this has size 4 andLOAD_METHOD
has size 10.This may be the source of your problem.
Are you using the two version numbers consistently?
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.