-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
bpo-35147: Fix _Py_NO_RETURN for GCC #10300
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
Conversation
Use __GNUC__ instead of non-existing __GNUC_MAJOR__.
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.
LGTM.
@izbyshev: Status check is done, and it's a success ✅ . |
Thanks @izbyshev for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6, 3.7. |
Sorry, @izbyshev, I could not cleanly backport this to |
Sorry, @izbyshev, I could not cleanly backport this to |
Use `__GNUC__` instead of non-existing `__GNUC_MAJOR__`. https://bugs.python.org/issue35147. (cherry picked from commit e2ed5ad) Co-authored-by: Alexey Izbyshev <[email protected]>
GH-10301 is a backport of this pull request to the 3.7 branch. |
Use `__GNUC__` instead of non-existing `__GNUC_MAJOR__`. https://bugs.python.org/issue35147. (cherry picked from commit e2ed5ad) Co-authored-by: Alexey Izbyshev <[email protected]>
GH-10302 is a backport of this pull request to the 3.6 branch. |
Use `__GNUC__` instead of non-existing `__GNUC_MAJOR__`. (cherry picked from commit e2ed5ad) https://bugs.python.org/issue35147
Use
__GNUC__
instead of non-existing__GNUC_MAJOR__
.https://bugs.python.org/issue35147