Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Motivation
Large statically generated game targets can exhaust linker memory even with a single link worker. A 107-translation-unit X-Men Legends runner exceeded a 2 GiB linker-process cap with IPO enabled. Disabling IPO only for the generated runner allowed the complete executable to link under the same cap while preserving /O2 and optimized/IPO-enabled runtime libraries.
The option defaults ON, so existing builds are unchanged.
Validation
Configured current upstream main with MSVC/Visual Studio 2022, CMAKE_BUILD_TYPE=Release, and global IPO enabled:
The 107-unit game runner was compiled with /O2 and no /GL, linked with /CGTHREADS:1 under the unchanged 2 GiB guard, passed PE section validation, and reached rendered gameplay.