The Windows build of Python does not need incremental linker support for release and PGO builds #92984
Labels
Comments
zooba
pushed a commit
that referenced
this issue
May 19, 2022
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
May 19, 2022
…lease and PGO builds (pythonGH-92985) (cherry picked from commit 38feffa) Co-authored-by: David Machaj <[email protected]>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
May 19, 2022
…lease and PGO builds (pythonGH-92985) (cherry picked from commit 38feffa) Co-authored-by: David Machaj <[email protected]>
miss-islington
added a commit
that referenced
this issue
May 19, 2022
…and PGO builds (GH-92985) (cherry picked from commit 38feffa) Co-authored-by: David Machaj <[email protected]>
miss-islington
added a commit
that referenced
this issue
May 19, 2022
…and PGO builds (GH-92985) (cherry picked from commit 38feffa) Co-authored-by: David Machaj <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
By default when the
/debugoption is specified for link.exe, so that it will produce a .pdb file, it will assume that incremental linking should also be enabled. Incremental linking creates an incompatibility with some binary analysis tools. Those tools, such as SizeBench are useful so I think it makes sense to disable incremental linking so that they can be used.Your environment
This behavior was verified using a fresh clone of this repo as of yesterday (main branch). I built using the most recent 17.2.0 toolset from Visual Studio 2022. After running
pcbuild/build.bat --pgoI was unable to analyze the resulting python312.dll file because of incremental linking.The text was updated successfully, but these errors were encountered: