Bug report
By default when the /debug option 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 --pgo I was unable to analyze the resulting python312.dll file because of incremental linking.
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.