-
-
Notifications
You must be signed in to change notification settings - Fork 32k
GH-130396: Broaden definition of "optimized" for gdb tests #130550
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
!buildbot AMD64.Fedora.Stable.Clang.3.x |
The regex 'AMD64.Fedora.Stable.Clang.3.x' did not match any buildbot builder. Is the requested builder in the list of stable builders? |
!buildbot Fedora.*Clang |
🤖 New build scheduled with the buildbot fleet by @markshannon for commit 3a3817e 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F130550%2Fmerge The command will test the builders whose names match following regular expression: The builders matched are:
|
Let's try again !buildbot Fedora.*Clang |
Once more for luck 🙂 !buildbot AMD.*Fedora.*Clang |
The buildbot workers used on GitHub are called "... PR", not "... 3.x". |
Python built with
Python built with
_PyObject_VectorcallTstate() is built differently:
|
Yes. Clang is tailcalling from But what do we do about the gdb tests? |
In my experience, python-gdb.py is not reliable with any optimization level higher than |
c9ab78d
to
909fe79
Compare
!buildbot AMD64.*Fedora.*Stable.*Clang |
🤖 New build scheduled with the buildbot fleet by @markshannon for commit 909fe79 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F130550%2Fmerge The command will test the builders whose names match following regular expression: The builders matched are:
|
I'm confused. Does Clang still optimize even with |
It depends what you mean by "optimize". |
Weird, I thought the whole point of Maybe for Clang it just means "don't confuse |
That's an old debate. In my experience with GCC and clang, -Og does optimize way too much for gdb which often fails to read function local variables and arguments ("<optimized out>"). |
Thanks @markshannon for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12. |
Thanks @markshannon for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Sorry, @markshannon, I could not cleanly backport this to
|
GH-130572 is a backport of this pull request to the 3.13 branch. |
GH-130573 is a backport of this pull request to the 3.12 branch. |
I backported the test_gdb fix to 3.12 and 3.13 branches. |
…ythonGH-130550) (pythonGH-130573) pythonGH-130396: Treat clang -Og as optimized for gdb tests (pythonGH-130550) (cherry picked from commit 129db32) (cherry picked from commit c4aeb4c) Co-authored-by: Victor Stinner <vstinner@python.org> Co-authored-by: Mark Shannon <mark@hotpy.org>
Uh oh!
There was an error while loading. Please reload this page.