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/27924] ld.so: Support DT_RELR relative relocation format Date: Tue, 19 Oct 2021 16:51:21 +0000 [thread overview] Message-ID: <bug-27924-131-W8TnNk6ilm@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27924-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27924 --- Comment #10 from Fangrui Song <i at maskray dot me> --- in-reply-to: https://bugzilla.redhat.com/show_bug.cgi?id=2014699#c1 > * [v2] elf: Support DT_RELR relative relocation format [BZ #27924] > * Need official gABI assignment (Carry Coutant status?) > * Needs to be reserved verbally by Carry (Action item) > * Required for patch acceptance. s/Carry/Cary. https://groups.google.com/g/generic-abi/c/bX460iggiKg/m/6psrcLHLAgAJ (2018-02) https://sourceware.org/bugzilla/show_bug.cgi?id=27924#c7 (2021-06) and https://sourceware.org/pipermail/libc-alpha/2021-October/131781.html are verbal by Cary. > * Need BFD port or a released llvm/lld that supports DT_RELR to review patches. > * Minimally a 32-bit and 64-bit port that can build glibc and passes regression testing. > * Required for patch review. LLD since 7.0.0 supports --pack-dyn-relocs=relr. Both arm and aarch64 ports have users. ld.lld --pack-dyn-relocs=relr produces working executables on Fuchsia, Linux kernel's arm64 port, FreeBSD-CURRENT, ChromeOS's (patched glibc) today. Just that the produced executable segfaults on glibc due to lack of support. > * Official glibc relese with feature? > * Need BFD port to support build-many-glibcs to provide testing confidence. > * HJ: Would like to see a BFD port before a glibc release with the features. > * Sufficient to have a released binutils with DT_RELR also. Wish that a GNU ld maintainer can work on this... > * Release date of released static linkers with support should be close to glibc release with feature. > * When glibc is released users can pick a static linker to test with (binutils or lld). LLD since 7.0.0 supports --pack-dyn-relocs=relr, so the release date (2018) cannot be close to the glibc version now... Even in the absence of GNU ld support, with DT_RELR support, users can use ld.lld --pack-dyn-relocs=relr today. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-10-19 16:51 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-27 18:14 [Bug dynamic-link/27924] New: " i at maskray dot me 2021-05-27 18:40 ` [Bug dynamic-link/27924] " i at maskray dot me 2021-05-27 19:01 ` i at maskray dot me 2021-05-27 23:20 ` i at maskray dot me 2021-06-24 16:08 ` carlos at redhat dot com 2021-06-24 16:08 ` carlos at redhat dot com 2021-06-24 16:30 ` carlos at redhat dot com 2021-06-24 18:03 ` i at maskray dot me 2021-06-24 18:15 ` carlos at redhat dot com 2021-06-24 21:38 ` ccoutant at gmail dot com 2021-06-24 21:38 ` ccoutant at gmail dot com 2021-10-08 21:52 ` i at maskray dot me 2021-10-15 22:00 ` sam at gentoo dot org 2021-10-19 13:11 ` carlos at redhat dot com 2021-10-19 16:51 ` i at maskray dot me [this message] 2021-10-25 13:47 ` fweimer at redhat dot com 2021-10-25 13:50 ` fweimer at redhat dot com 2022-01-05 0:25 ` hjl.tools at gmail dot com 2022-01-05 1:11 ` i at maskray dot me 2022-01-05 1:49 ` hjl.tools at gmail dot com 2022-01-05 1:50 ` hjl.tools at gmail dot com 2022-01-05 3:27 ` i at maskray dot me 2022-01-05 3:39 ` hjl.tools at gmail dot com 2022-01-05 3:42 ` hjl.tools at gmail dot com 2022-01-05 22:54 ` hjl.tools at gmail dot com 2022-01-08 20:36 ` hjl.tools at gmail dot com 2022-01-09 17:10 ` hjl.tools at gmail dot com 2022-06-07 8:05 ` i at maskray dot me
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-27924-131-W8TnNk6ilm@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).