{{ message }}
GH-125174: Mark objects as statically allocated.#127797
Merged
markshannon merged 11 commits intoDec 11, 2024
Merged
Conversation
ericsnowcurrently
left a comment
Member
There was a problem hiding this comment.
Mostly LGTM. I've left a couple of minor comments. This will be a nice improvement.
Sorry, something went wrong.
Member
|
Out of curiosity, how disruptive is adding a new field to the object structure? |
Sorry, something went wrong.
Member
Author
It doesn't change the size of the |
Sorry, something went wrong.
0e7513a to
3788c60
Compare
December 11, 2024 10:11
ericsnowcurrently
approved these changes
Dec 11, 2024
ericsnowcurrently
left a comment
Member
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
encukou
reviewed
Dec 12, 2024
srinivasreddy
pushed a commit
to srinivasreddy/cpython
that referenced
this pull request
Jan 8, 2025
* Set a bit in the unused part of the refcount on 64 bit machines and the free-threaded build. * Use the top of the refcount range on 32 bit machines
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
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.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.

This PR is a follow up to #125251 which made checking for immortal objects more robust.
This adds the ability to check whether objects are statically allocated or not, which should assist finalization and safety checks.