8000 [3.6] bpo-38965: Fix faulthandler._stack_overflow() on GCC 10 (GH-17467) by miss-islington · Pull Request #28079 · python/cpython · GitHub
[go: up one dir, main page]
Skip to content

[3.6] bpo-38965: Fix faulthandler._stack_overflow() on GCC 10 (GH-17467) #28079

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Aug 31, 2021
Merged

[3.6] bpo-38965: Fix faulthandler._stack_overflow() on GCC 10 (GH-17467) #28079

merged 1 commit into from
Aug 31, 2021

Conversation

miss-islington
Copy link
Contributor
@miss-islington miss-islington commented Aug 31, 2021 •
edited by bedevere-bot
Loading

Use the "volatile" keyword to prevent tail call optimization
on any compiler, rather than relying on compiler specific pragma.
(cherry picked from commit 8b78796)

Co-authored-by: Victor Stinner vstinner@python.org
(cherry picked from commit 5044c88)

Co-authored-by: Miss Islington (bot) 31488909+miss-islington@users.noreply.github.com

https://bugs.python.org/issue38965

@miss-islington
bpo-38965: Fix faulthandler._stack_overflow() on GCC 10 (pythonGH-17467)
d071387 
Use the "volatile" keyword to prevent tail call optimization
on any compiler, rather than relying on compiler specific pragma.
(cherry picked from commit 8b78796)

Co-authored-by: Victor Stinner <vstinner@python.org>
(cherry picked from commit 5044c88)

Co-authored-by: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
@miss-islington
Copy link
Contributor Author

@vstinner: Status check is done, and it's a success ✅ .

@ned-deily ned-deily merged commit 8934bb0 into python:3.6 Aug 31, 2021
@miss-islington miss-islington deleted the backport-5044c88-3.6 branch August 31, 2021 06:24
@miss-islington
Copy link
Contributor Author

@vstinner: Status check is done, and it's a failure ❌ .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@miss-islington @ned-deily @the-knights-who-say-ni @bedevere-bot
0