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-35147: Fix _Py_NO_RETURN for GCC #10300
Conversation
Use __GNUC__ instead of non-existing __GNUC_MAJOR__.
@izbyshev: Status check is done, and it's a success |
Thanks @izbyshev for the PR |
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 <izbyshev@ispras.ru>
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 <izbyshev@ispras.ru>
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