gh-130419: Do not build the _freeze_module twice in case of Windows PGO builds #130420
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.