From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>,
Binutils <binutils@sourceware.org>
Subject: Re: RFC: Add GNU_PROPERTY_1_GLIBC_2_NEEDED
Date: Fri, 29 Oct 2021 20:11:23 +0200 [thread overview]
Message-ID: <87r1c3itv8.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAMe9rOrdOkPq0OviBMHhKfHP3XrdynDZorf0GnWQzQr_s9kuZg@mail.gmail.com> (H. J. Lu's message of "Thu, 28 Oct 2021 07:20:32 -0700")
* H. J. Lu:
> How do we deal with
>
> Somes binaries compiled with the new language features, like C2X
> printf specifiers, only generate correct results with the new glibc
> binary. Since we don't add new glibc versions to the printf function
> family, they generate incorrect results at run-time with the older
> glibc binaries.
We decided not to use symbol versions for that. Likewise for support
for new flags in e.g. dlopen. We also do not od this for system calls
and system call flags.
If an application uses the new printf specifiers, it can probe for
support at run time and register its own implementation if necessary.
This is a bit complicated, but it's how applications are expected to
handle new flags in older interfaces.
Thanks,
Florian
next prev parent reply other threads:[~2021-10-29 18:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 14:53 H.J. Lu
2021-10-26 15:25 ` Florian Weimer
2021-10-26 15:51 ` H.J. Lu
2021-10-26 18:39 ` v2: " H.J. Lu
2021-10-28 6:55 ` Florian Weimer
2021-10-28 13:37 ` H.J. Lu
2021-10-28 14:08 ` Florian Weimer
2021-10-28 14:17 ` H.J. Lu
2021-10-28 14:20 ` H.J. Lu
2021-10-29 18:11 ` Florian Weimer [this message]
2021-10-29 12:47 ` Michael Matz
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=87r1c3itv8.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.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).