From: "Fāng-ruì Sòng via Libc-alpha" <libc-alpha@sourceware.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH v2 3/3] configure: Allow LD to be LLD 13.0.0 or above [BZ #26558]
Date: Sun, 22 Aug 2021 20:18:50 -0700 [thread overview]
Message-ID: <CAFP8O3LxK5DAvTdDxSogNoB1T+-J6skwfJ6-So3hGQ1vqDpWfw@mail.gmail.com> (raw)
In-Reply-To: <20210810221915.g6ipyceykaio3324@google.com>
On Tue, Aug 10, 2021 at 3:19 PM Fangrui Song <maskray@google.com> wrote:
>
> On 2021-08-05, Fangrui Song wrote:
> >When using LLD (LLVM linker) as the linker, configure prints a confusing
> >message.
> >
> > *** These critical programs are missing or too old: GNU ld
> >
> >LLD>=13.0.0 can build glibc --enable-static-pie. (8.0.0 needs one
> >workaround for -Wl,-defsym=_begin=0. 9.0.0 works with
> >--disable-static-pie).
> >
> >With BZ #28153 (glibc bug exposed by testing with LLD) fixed,
> >`make check` only has 2 more failures with LLD than with GNU ld:
> >BZ #28154 (LLD follows the PowerPC port of GNU ld for ifunc by
> >placing IRELATIVE relocations in .rela.dyn).
> >The set of dynamic symbols is the same with GNU ld and LLD,
> >modulo unused SHN_ABS version node symbols.
> >
> >For comparison, gold does not support --enable-static-pie
> >yet (--no-dynamic-linker is unsupported BZ #22221), yet
> >has 6 failures more than LLD. gold linked libc.so has
> >larger .dynsym differences with GNU ld and LLD
> >(ISTM non-default version symbols are changed to default versions
> >by a version script).
> >
> >---
> >
> >I identified the lack of support of
> >
> >* version script on non-default version symbols
> >* copy relocations on non-default version symbols
> >
> >in an earlier snapshot of LLD 13.0.0 and fixed them.
> >The functionality of the LLD linked libc.so and ld.so looks pretty good.
> >---
> > configure | 77 +++++++++++++++++++++++++++++++++++++++++++++++++---
> > configure.ac | 20 ++++++++++----
> > 2 files changed, 88 insertions(+), 9 deletions(-)
>
> Ping:)
>
> (The code/test hasn't been changed since v1.
> v2 just added BZ numbers.)
>
> x86-64 only 2 more ifunc FAIL which tickle some weak point of ifunc implementation.
>
> aarch64 `make-check` is fully on par with GNU ld.
> (https://sourceware.org/pipermail/libc-alpha/2021-August/130040.html)
Ping^2
("elf: Replace .tls_common with .tbss definition [BZ #28152]" has been
subsumed into a tls-macros.h removal patch.)
next prev parent reply other threads:[~2021-08-23 3:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 16:25 [PATCH v2 0/3] Allow LLD 13.0.0 and improve compatibility with gold and clang Fangrui Song via Libc-alpha
2021-08-05 16:25 ` [PATCH v2 1/3] elf: Replace .tls_common with .tbss definition [BZ #28152] Fangrui Song via Libc-alpha
2021-08-05 16:26 ` [PATCH v2 2/3] elf: Skip tst-auditlogmod-* if the linker doesn't support --depaudit [BZ #28151] Fangrui Song via Libc-alpha
2021-08-16 4:59 ` Fāng-ruì Sòng via Libc-alpha
2021-08-24 3:56 ` Fāng-ruì Sòng via Libc-alpha
2021-08-24 12:04 ` Adhemerval Zanella via Libc-alpha
2021-08-05 16:26 ` [PATCH v2 3/3] configure: Allow LD to be LLD 13.0.0 or above [BZ #26558] Fangrui Song via Libc-alpha
2021-08-05 16:34 ` H.J. Lu via Libc-alpha
2021-08-05 16:43 ` Fāng-ruì Sòng via Libc-alpha
2021-08-05 17:04 ` H.J. Lu via Libc-alpha
2021-08-07 0:47 ` Fāng-ruì Sòng via Libc-alpha
2021-08-07 13:15 ` H.J. Lu via Libc-alpha
2021-08-08 4:17 ` Fāng-ruì Sòng via Libc-alpha
2021-08-09 17:58 ` H.J. Lu via Libc-alpha
2021-08-09 19:58 ` Fāng-ruì Sòng via Libc-alpha
2021-08-10 14:38 ` H.J. Lu via Libc-alpha
2021-08-10 17:42 ` Fāng-ruì Sòng via Libc-alpha
2021-08-10 22:19 ` Fangrui Song via Libc-alpha
2021-08-23 3:18 ` Fāng-ruì Sòng via Libc-alpha [this message]
2021-08-24 17:05 ` Fāng-ruì Sòng via Libc-alpha
2021-08-30 19:52 ` Fāng-ruì Sòng via Libc-alpha
2021-08-30 20:01 ` Adhemerval Zanella via Libc-alpha
2021-08-31 21:24 ` Fāng-ruì Sòng via Libc-alpha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFP8O3LxK5DAvTdDxSogNoB1T+-J6skwfJ6-So3hGQ1vqDpWfw@mail.gmail.com \
--to=libc-alpha@sourceware.org \
--cc=maskray@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).