Skip to content

Consider using incremental linking with msvc #37543

Open
Open
Consider using incremental linking with msvc#37543
Labels
A-linkageArea: linking into static, shared libraries and binariesC-enhancementCategory: An issue proposing an enhancement or a PR with one.I-compiletimeIssue: Problems and improvements with respect to compile times.O-windows-msvcToolchain: MSVC, Operating system: WindowsT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
@retep998

Description

@retep998
retep998
opened on Nov 2, 2016

Incremental linking will allow for significantly faster link times, at the cost of binary size.

  1. Don't delete the output artifacts. The .ilk and .exe or .dll must remain from the previous run.
  2. Don't pass /OPT to the linker or any other flag that is mutually exclusive with incremental linking.
  3. Pass /INCREMENTAL to the linker.
  4. The set of files passed to the linker must remain the same. If the codegen unit object files change names, then it will do a full link.

https://msdn.microsoft.com/en-us/library/4khtbfyf.aspx

Alternatively, provide LLD as a stable alternative to link.exe so users can benefit from faster links when they don't need any special features of link.exe.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-linkageArea: linking into static, shared libraries and binariesC-enhancementCategory: An issue proposing an enhancement or a PR with one.I-compiletimeIssue: Problems and improvements with respect to compile times.O-windows-msvcToolchain: MSVC, Operating system: WindowsT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions