public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/29651] glibc can't handle IRELATIVE in .rel.plt only on ARM32 and PPC Date: Thu, 13 Oct 2022 17:41:55 +0000 [thread overview] Message-ID: <bug-29651-131-s0EyiIxWli@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29651-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29651 Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adhemerval.zanella at linaro dot o | |rg --- Comment #1 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> --- It was already reported on binutils [1] and on lld [2]. The current behavior for ld on arm is to put IRELATIVE on .rel.dyn but I am not sure why exactly (Peter hinted it is a "legacy of ARM having a single .got section", and I am not sure if ld still have this limitation yet). So 'fixing' it won't gain us anything with current supported static linkers. It might improve support on arm ifunc itself (for instance to be able to call R_ARM_JUMP_SLOT functions, since ifunc will be reordered last), but what ifunc is able to do is not properly documented and has a lot of pitafalls that calling external functions (from current TU) is always 'tricky'. And even if we change it, a static-linker that only emits IRELATIVE on .rel.plt will need to prevent to run on older glibc (as we did for DT_RELR with a extra symbol). So the question is whether you need this changed. Do you need it for your mold linker? [1] https://sourceware.org/bugzilla/show_bug.cgi?id=19891 [2] https://reviews.llvm.org/D26029 [3] https://sourceware.org/glibc/wiki/GNU_IFUNC -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-10-13 17:41 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-04 2:39 [Bug libc/29651] New: " rui314 at gmail dot com 2022-10-04 2:43 ` [Bug libc/29651] " rui314 at gmail dot com 2022-10-13 17:41 ` adhemerval.zanella at linaro dot org [this message] 2022-10-14 1:48 ` rui314 at gmail dot com 2022-10-14 12:16 ` adhemerval.zanella at linaro dot org 2022-10-14 13:40 ` adhemerval.zanella at linaro dot org 2022-10-15 2:06 ` rui314 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-29651-131-s0EyiIxWli@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: linkBe 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).