[llvm-bugs] [Bug 24740] [ms] clang-cl produces .obj files that link.exe mis-links in /incremental mode

via llvm-bugs llvm-bugs at lists.llvm.org
Sat Dec 26 09:04:30 PST 2015


Nico Weber <nicolasweber at gmx.de> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Nico Weber <nicolasweber at gmx.de> ---
LLVM 256203 added an MC target option to toggle writing of timestamps. r256204
added a /Brepro flag to clang-cl mode to set this option for clang-cl, and it
also made it so it's not set in mingw builds:

+  // Only default to -mincremental-linker-compatible if we think we are
+  // targeting the MSVC linker.
+  bool DefaultIncrementalLinkerCompatible =
+      C.getDefaultToolChain().getTriple().isWindowsMSVCEnvironment();

There's still no flag to set an explicit timestamp from the driver as motivated
in comment 2, but the main issue here was fixed by David. (If the explicit
timestamp override turns out to be useful in the future, we can add it then.)

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20151226/ccc1c368/attachment-0001.html>

More information about the llvm-bugs mailing list