[cfe-dev] Why isn't LD.LLD a drop-in replacement for GNU LD when built on Windows as part of a MinGW-W64 based LLVM/Clang toolchain?

[Ben Grasset via cfe-dev]

As far as I can tell, it is literally the only tool in the entire
LLVM/Clang ecosystem for which this is the case.

I.E. clang.exe works as a direct replacement for MinGW gcc.exe. clang++.exe
works as a direct replacement for MinGW g++.exe. llvm-objcopy works as a
direct replacement for MinGW objcopy.exe. llvm-objdump works as a direct
replacement for MinGW objdump.exe. And so on.

Is it just one of those unfortunate worked-out-that-way-historically sort
of things? Looking at the source repository it seems like there are a lot
of things developed in the ELF folder that probably shouldn't be
ELF-specific, for example LinkerScript.cpp. To my mind linker script
parsing has no reason to specifically by an "ELF" thing.

Are there any current plans to bridge this compatibility gap in the future?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20181214/45642431/attachment.html>