| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…ute it all the time when tracing.
…rsion of Python used.
|
Probably the issue should be renamed to ... Backport GH-93769 for a clickable number in https://github.com/python/cpython/commits/main (though, it's just a nitpick). |
Sorry, something went wrong.
|
@pablogsal I'd like to get this merged, as it will be needed for the backport of #94371 |
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good to me 👍
Sorry, something went wrong.
I can try to do it for you. Otherwise you can follow these instructions: |
Sorry, something went wrong.
|
I cannot push to the PR, but you can copy this commit into yours if you want: |
Sorry, something went wrong.
|
Hmm, I followed the instructions, yet a0ced71 is clearly different to pablogsal@8380dd0 |
Sorry, something went wrong.
|
I see, it is because of the assert changing the line numbers. |
Sorry, something went wrong.
Those are not taken into account when checking it. They just come from the DWARF if I am not mistaken |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM !
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Reduces the overhead of dispatching in DO_TRACING considerably.
My informal measures on the test program in #93516 (comment) show that this reduces execution time by about 10%
@pablogsal Should I regenerate the ABI for this PR?