bpo-33608: Fix the Py_atomic_* macros.#12240
Merged
ericsnowcurrently merged 1 commit intopython:masterfrom Mar 8, 2019
Merged
Conversation
|
@ericsnowcurrently: Please replace |
|
Member
Author
|
I'm pretty sure this isn't due to this commit. |
paulmon
reviewed
Mar 20, 2019
| switch (ORDER) { \ | ||
| case _Py_memory_order_acquire: \ | ||
| _InterlockedExchange_acq((volatile long*)ATOMIC_VAL, (int)NEW_VAL); \ | ||
| _InterlockedExchange_acq((volatile long*)&((ATOMIC_VAL)->_value), (int)NEW_VAL); \ |
Contributor
There was a problem hiding this comment.
This ends up evaluating to _InterlockedExchange_acq((volatile long*)&((&((&_PyRuntime.ceval.gil.last_holder)->_value))->_value) causing a build error for _M_ARM
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.
The macros currently work because our usage happens to parse correctly. I ran into the problem while working on a PR (for bpo-33608) that involves a pointer indirection.
Note that this was part of a PR (gh-12062) that already landed and had to be reverted. This is the part that was unrelated to the need to revert.
https://bugs.python.org/issue33608