New issue
Advanced search Search tips

Issue 679089 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug

Blocking:
issue 787983



Sign in to add a comment

See if incremental linking can be enabled for x64 in goma/symbol_level=1 builds

Project Member Reported by brucedaw...@chromium.org, Jan 7 2017

Issue description

Incremental linking is off for some modules for x64 builds due to VC++ limitations. However in goma builds, such as these settings:

enable_nacl = false
is_component_build = true
is_debug = true
use_goma = true

it can probably be enabled.

These are the relevant settings and they are very confusing:

https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/BUILD.gn?rcl=0&l=216
https://cs.chromium.org/chromium/src/build/config/win/BUILD.gn?rcl=0&l=366

 
Note that VC++ 2017 Update 1 increases the ILK file limits (removes them entirely?) such that we should be able to enable incremental linking everywhere.
Blocking: 495670
Blocking: 787983
Blocking: -495670
Note that use_lld=true is now recommended (it is faster for full builds and avoids the problems associated with is_win_fastlink=true) and it doesn't currently support incremental linking, making this bug irrelevant in the near term.
Status: Fixed (was: Assigned)
The switch to lld makes this irrelevant or fixed, depending on how you look at it.

Incremental linking is now "enabled" on x64 builds (as of crrev.com/c/1092611) so that we get the optimization where import libraries aren't unnecessarily rewritten when /incremental is specified, and that's all that we can do.

Sign in to add a comment