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, 07 Jun 2022 08:05:19 +0000 [thread overview]
Message-ID: <bug-27924-131-j8YE2aNMvv@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27924-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27924
Fangrui Song <i at maskray dot me> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #21 from Fangrui Song <i at maskray dot me> ---
Resolved by some changes pushed on 2022-04-26:
https://sourceware.org/pipermail/libc-alpha/2022-April/138085.html ([PATCH v11
0/7] Support DT_RELR relative relocation format)
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-06-07 8:05 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
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 [this message]
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-j8YE2aNMvv@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).