public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "i at maskray dot me" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/28154] [test] sysdeps/x86/tst-ifunc-isa-* lazy binding failure with ld.lld
Date: Thu, 29 Jul 2021 22:54:24 +0000 [thread overview]
Message-ID: <bug-28154-131-AOG5uhOeUP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28154-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28154
Fangrui Song <i at maskray dot me> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amodra at gmail dot com
--- Comment #2 from Fangrui Song <i at maskray dot me> ---
(In reply to H.J. Lu from comment #1)
> See PR ld/13302. lld should implement the same behavior.
I think the GNU ld PowerPC (ld.lld) behavior (IRELATIVE in .rela.dyn) makes
more sense. IRELATIVE relocations are eagerly resolved, so .rela.dyn is better
than .rela.plt . .rela.plt should only have JUMP_SLOT.
To make PR ld/13302 work, ld.so can pause at IRELATIVE in .rela.dyn and start
applying .rela.plt
(I use the section names for simplicity. Impl should use dynamic tags
DT_RELA/DT_JMPREL.)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-07-29 22:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 21:15 [Bug dynamic-link/28154] New: " i at maskray dot me
2021-07-29 22:21 ` [Bug dynamic-link/28154] " hjl.tools at gmail dot com
2021-07-29 22:54 ` i at maskray dot me [this message]
2021-07-29 23:07 ` hjl.tools at gmail dot com
2021-09-01 5:43 ` cvs-commit at gcc dot gnu.org
2024-04-24 7:10 ` amodra at gmail dot com
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-28154-131-AOG5uhOeUP@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/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).