GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||||||||||
GeezerVison is showing github.com — gh-128563: Move lltrace into the frame struct by Fidget-Spinner · Pull Request #129113 · python/cpython Conversation
|
|
When you're done making the requested changes, leave the comment: |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I have made the requested changes; please review again. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thanks for making the requested changes! @markshannon: please review the changes made to this pull request. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| char owner; | ||
| #ifdef Py_DEBUG | ||
| char visited:4; | ||
| char lltrace:4; |
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Why 4?
You only need one bit (although it is best to use uint8_t as the signedness of char is implementation defined.
My mistake, lltrace is not boolean.
Since char might be signed, it is best to make this a uint8_t to avoid overflow for PYTHON_LLTRACE=9
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
One small issue, otherwise looks good.
lltrace should be unsigned (uint8_t), and maybe bigger, to avoid overflow. visited only needs one bit, so lltrace could use the rest.
For consistency, make visited a uint8_t in the non-debug build as well.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sorry for being late here. These lines seem to be unused, since the PR did not have to touch them? Lines 1066 to 1071 in 05d12ee
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@chris-eibl it seems so. If you would like to, could you please open a PR to either update to fix them or remove them? Thanks! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Yeah, but since this is gonna be my first PR, I'll have to work myself through the devguide. Most probably not before the weekend ... |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.