public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/27924] ld.so: Support DT_RELR relative relocation format Date: Thu, 24 Jun 2021 16:08:08 +0000 [thread overview] Message-ID: <bug-27924-131-xYFaLIyZUV@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27924-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27924 Carlos O'Donell <carlos at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carlos at redhat dot com --- Comment #3 from Carlos O'Donell <carlos at redhat dot com> --- The proposal to the ABI seems stalled and probably needs to be pushed again to the gABI group with the updated wording for review again? The alternative is not to extend the gABI but consider this a GNU ABI extension. If Google has interest in moving this forward someone needs to be a change champion here and work with upstream. Objectively I have no problem with SHT_RELR, but it should be documented in our ABI docs *somewhere* so we have a concrete place to discuss future changes and accept those changes. Today the gABI list is a "consensus" group with Cary Coutant documenting that consensus. The GNU ABI is implemented by the GNU Toolchain, so there is probably some consensus there that needs forming, but we can do that too. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-06-24 16:08 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 [this message] 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 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-xYFaLIyZUV@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).