[PATCH] D12029: [lld] LinkDriver, lld-link: introduce shim.

[Reid Kleckner via llvm-commits]

rnk added a subscriber: rnk.
rnk added a comment.

BFD ld has some options that link.exe doesn't have. If we do aliasing and argument translation, what will we do for such options? Invent our own link.exe-style options? Or try to pass through the BFD option?

Based on our experience with clang vs clang-cl, I think we want to implement a driver that consumes all options, aliases everything that can be aliased, and treats the ld-style flags as first class citizens. In retrospect, I wish that clang-cl used a blacklist approach, where incompatible GCC-style flags are blacklisted, rather than whitelisting core options one by one. If there aren't any conflicts between link.exe and gnu ld flags, we can go ahead and do this.

We can avoid duplicating the common options between ELF and COFF by generating a single option table and adding COFF / ELF flags like we do for clang / clang-cc1.


http://reviews.llvm.org/D12029