Some known issues:
* elf/librtld.map.o uses a subtle property of --defsym: https://sourceware.org/pipermail/libc-alpha/2020-April/112732.html
* ld.lld --verbose does not print a linker script and ld.lld --print-output-format is not supported: https://sourceware.org/pipermail/libc-alpha/2020-April/112733.html
* Neither clang nor LLD may support the semantics of .tls_common https://sourceware.org/pipermail/libc-alpha/2020-April/112734.html
(In reply to Fangrui Song from comment #0)
> Some known issues:
> * elf/librtld.map.o uses a subtle property of --defsym:
Since --defsym in ldd is incompatible with glibc build, --defsym should be
poisoned for glibc build.
> * ld.lld --verbose does not print a linker script and ld.lld
> --print-output-format is not supported:
> * Neither clang nor LLD may support the semantics of .tls_common
This is used to implement STT_COMMON. Do clang/LLD support STT_COMMON?
I think you should make your glibc branch for lld available so that people
can give it a try.
Before lld can be accepted for glibc build, it must generate the same set
of failures in glibc testsuite with binutils 2.35 at least on i686 and x86-64.