From: Joseph Myers <joseph@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Binutils <binutils@sourceware.org>
Subject: Re: [PATCH v2] elf: Support DT_RELR relative relocation format [BZ #27924]
Date: Mon, 18 Oct 2021 23:44:49 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2110182339050.139834@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAMe9rOoinGTOYRxzXfwZznFCZAADk4pBt531V1SuDcZ_whNtkw@mail.gmail.com>
On Mon, 18 Oct 2021, H.J. Lu via Libc-alpha wrote:
> Ideally when the new specifiers are used, it should require the new
> glibc version. Is there a way to do it?
I don't think there's any sensible way to do it. You'd need new symbol
versions (aliased to the old ones, not actual separate entry points with
different addresses) for all the 70 or so printf-like functions (twice
that number when two long double variants are supported, three times that
number when three long double variants are supported). That's not
something we've done before for new printf/scanf/strftime/strfmon formats.
The scanf changes will get new __isoc23_* entry points because of API
differences with scanf %i (but someone could still e.g. use scanf %b when
building for strict C11, and so get a binary using the old entry point
with a new format that doesn't work with older glibc - there would only be
the 32 / 44 / 56 new entry points, not new symbol versions for old entry
points).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-10-18 23:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 0:50 Fangrui Song
2021-10-18 14:42 ` H.J. Lu
2021-10-18 16:16 ` Fāng-ruì Sòng
2021-10-18 17:28 ` H.J. Lu
2021-10-18 18:15 ` Fāng-ruì Sòng
2021-10-18 18:27 ` H.J. Lu
2021-10-18 19:19 ` Fāng-ruì Sòng
2021-10-18 19:44 ` H.J. Lu
2021-10-18 20:11 ` Fāng-ruì Sòng
2021-10-18 21:10 ` Joseph Myers
2021-10-18 22:27 ` H.J. Lu
2021-10-18 22:30 ` Joseph Myers
2021-10-18 22:42 ` H.J. Lu
2021-10-18 23:00 ` Joseph Myers
2021-10-18 23:36 ` H.J. Lu
2021-10-18 23:44 ` Joseph Myers [this message]
2021-10-19 1:05 ` H.J. Lu
2021-10-18 19:21 ` Joseph Myers
2021-10-18 19:45 ` H.J. Lu
2021-10-29 18:21 ` Carlos O'Donell
2021-10-29 18:36 ` H.J. Lu
2021-10-29 19:15 ` Fangrui Song
2021-10-29 18:38 ` Fāng-ruì Sòng
2021-10-29 19:35 ` Carlos O'Donell
2021-10-29 19:53 ` Adhemerval Zanella
2021-11-01 4:50 ` Fāng-ruì Sòng
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=alpine.DEB.2.22.394.2110182339050.139834@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@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).