-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
GH-141808: Do not generate the jit stencils twice in case of PGO builds on Windows. #142043
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
|
🤖 New build scheduled with the buildbot fleet by @gpshead for commit fb17f11 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F142043%2Fmerge If you want to schedule another build, you need to add the 🔨 test-with-buildbots label again. |
|
Thanks @chris-eibl for the PR, and @gpshead for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
…O builds on Windows. (pythonGH-142043) * do not build the jit stencils twice in case of PGO builds on Windows * blurb it (cherry picked from commit f2ca158) Co-authored-by: Chris Eibl <[email protected]>
|
GH-142100 is a backport of this pull request to the 3.14 branch. |
…GO builds on Windows. (GH-142043) (#142100) GH-141808: Do not generate the jit stencils twice in case of PGO builds on Windows. (GH-142043) * do not build the jit stencils twice in case of PGO builds on Windows * blurb it (cherry picked from commit f2ca158) Co-authored-by: Chris Eibl <[email protected]>
…O builds on Windows. (pythonGH-142043) * do not build the jit stencils twice in case of PGO builds on Windows * blurb it
Just re-use them in the PGUpdate phase: by using the same folder as in the PGInstrument phase, the hash will just match and the stencils are not built again. This saves time, especially on old PCs like mine, where the stencils generation takes about a minute.