Skip to content

gh-130419: Do not build the _freeze_module twice in case of Windows PGO builds #130420

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

Merged
merged 1 commit into from
Feb 24, 2025

Conversation

chris-eibl
Copy link
Member

@chris-eibl chris-eibl commented Feb 21, 2025

Make the Windows PGO build slightly faster by not building the _freeze_module again in the PGUpdate phase.

I think this is a skip-news?

This will also speed up clang-cl PGO build time (#130090).

Using the same idea, all projects with SupportPGO=False could be built only once (mostly _test modules), but I think this is not worth the effort.

in case of Windows PGO builds
@chris-eibl
Copy link
Member Author

@zooba I think this is an easy one?

@zooba
Copy link
Member

zooba commented Feb 24, 2025

Should be easy, yes, but I'm running a test release to be sure.

@chris-eibl
Copy link
Member Author

Yeah, always good to double check :)

@zooba
Copy link
Member

zooba commented Feb 24, 2025

My extra test was good, so this is okay to merge. GitHub appears to be unhappy about something today though, so my merge isn't going through. If someone else manages to get it to merge, then go ahead!

@zooba zooba merged commit 3a555f0 into python:main Feb 24, 2025
42 checks passed
@chris-eibl chris-eibl deleted the skip_freeze_pgupdate branch February 25, 2025 15:35
seehwan pushed a commit to seehwan/cpython that referenced this pull request Apr 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants