link.Elf: Skip invoking LLD for zig build-obj for unsupported targets.

LLD doesn't support these yet. Doing this hack will at least allow basic
experimentation for these targets.
This commit is contained in:
Alex Rønne Petersen 2025-04-26 16:51:16 +02:00
parent b16c094926
commit 3e7708b02b
No known key found for this signature in database

View file

@ -1663,7 +1663,18 @@ fn linkWithLLD(self: *Elf, arena: Allocator, tid: Zcu.PerThread.Id, prog_node: s
// copy when generating relocatables. Normally, we would expect `lld -r` to work.
// However, because LLD wants to resolve BPF relocations which it shouldn't, it fails
// before even generating the relocatable.
if (output_mode == .Obj and (comp.config.lto != .none or target.cpu.arch.isBpf())) {
//
// For m68k, we go through this path because LLD doesn't support it yet, but LLVM can
// produce usable object files.
if (output_mode == .Obj and
(comp.config.lto != .none or
target.cpu.arch.isBpf() or
target.cpu.arch == .lanai or
target.cpu.arch == .m68k or
target.cpu.arch.isSPARC() or
target.cpu.arch == .ve or
target.cpu.arch == .xcore))
{
// In this case we must do a simple file copy
// here. TODO: think carefully about how we can avoid this redundant operation when doing
// build-obj. See also the corresponding TODO in linkAsArchive.