danalbert added a comment. @MaskRay Any other ideas, or should I submit this? Reviewing all our options:
1. Installing LLD as simply "ld" Rejected: Causes LLD to act in mach-o mode for Darwin 2. `-DCLANG_DEFAULT_LINKER=lld` Rejected: Our host Darwin toolchain still uses the system's linker, not LLD, and this would change that too (and as you said, the mach-o support in LLD isn't ready and is about to be replaces, so we can't do this for our production toolchain). 3. Using a wrapper script to set `-flavor gnu` Rejected: Wrappers don't work well on Windows hosts. 4. Teach LLD that Linux targets are `-flavor gnu`, regardless of host. LLD doesn't seem to differentiate between Android and non-Android Linux, so this change would affect non-Android Linux targets as well. Is that a problem? Do non-Android Linux targets linked from Windows, Darwin, or WebASM want the host driver modes the //target// driver modes? 5. This patch. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D76452/new/ https://reviews.llvm.org/D76452 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
