From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: "H.J. Lu via llvm-dev" <llvm-dev@lists.llvm.org>,
GNU C Library <libc-alpha@sourceware.org>,
Binutils <binutils@sourceware.org>,
GCC Development <gcc@gcc.gnu.org>,
GNU gABI gnu-gabi <gnu-gabi@sourceware.org>
Subject: Re: [llvm-dev] [PATCH] Add GNU_PROPERTY_1_GLIBC_2_NEEDED
Date: Thu, 28 Oct 2021 15:43:13 +0200 [thread overview]
Message-ID: <87lf2dl0y6.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAMe9rOpwy0FcxD+VontL3TPbhShT2GAm4i9zWfzi3XEW5FaeAg@mail.gmail.com> (H. J. Lu's message of "Thu, 28 Oct 2021 06:39:46 -0700")
* H. J. Lu:
> On Wed, Oct 27, 2021 at 11:52 PM Florian Weimer <fweimer@redhat.com> wrote:
>>
>> * H. J. Lu via llvm-dev:
>>
>> > 1. Some binaries which require new ELF features, like DT_RELR, only
>> > work with the new glibc binary. They crash at run-time with the older
>> > glibc binaries.
>> > 2. 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.
>>
>> Solaris uses SHT_SUNW_verneed sections for this, not a property note.
>> Property notes seem the wrong approach for this. And there is no reason
>> to make this specific to glibc.
>>
>> However, I still very much dislike this proposal.
>>
>
> Can you share your concerns?
See the other thread (mostly on libc-alpha I think).
Florian
next prev parent reply other threads:[~2021-10-28 13:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 0:03 H.J. Lu
2021-10-28 6:52 ` [llvm-dev] " Florian Weimer
2021-10-28 13:39 ` H.J. Lu
2021-10-28 13:43 ` Florian Weimer [this message]
2021-10-28 13:46 ` H.J. Lu
2021-10-28 17:43 ` Joseph Myers
2021-10-28 19:08 ` H.J. Lu
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=87lf2dl0y6.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gnu-gabi@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=llvm-dev@lists.llvm.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).