From: Vincent Chen <vincent.chen@sifive.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
darius@bluespec.com, dj@redhat.com
Subject: Re: [RFC PATCH] riscv: Add support for STT_GNU_IFUNC symbols
Date: Fri, 17 Jul 2020 10:53:36 +0800 [thread overview]
Message-ID: <CABvJ_xhnKpQznneD+9ONHXOkvEGGVwi=qRBJ_oQ35mooSzztGQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2007091624340.10450@digraph.polyomino.org.uk>
On Fri, Jul 10, 2020 at 12:40 AM Joseph Myers <joseph@codesourcery.com> wrote:
>
> On Thu, 9 Jul 2020, Vincent Chen wrote:
>
> > This patch adds the support for STT_GNU_IFUNC symbols to riscv ports. The
> > Binutils' IFUNC patches are under reviewing and can be found in
> > https://sourceware.org/pipermail/binutils/2020-July/112186.html.
> >
> > Any suggestions and feedback are welcome.
>
> We have the libc-abis mechanism that's supposed to ensure binaries using
> newer ELF features don't run on older glibc versions not implementing
> those features. So in theory an architecture newly getting IFUNC support
> should get a libc-abis entry (at the end of the file, not with the other
> IFUNC entries there). But given the various missing or broken pieces of
> this mechanism (EI_ABIVERSION not set in the static linker for most
> architectures, possibly not checked by glibc in some cases), that probably
> doesn't matter much.
>
> https://sourceware.org/legacy-ml/libc-ports/2010-03/msg00044.html
> https://sourceware.org/legacy-ml/libc-alpha/2010-04/msg00016.html
> https://sourceware.org/legacy-ml/libc-alpha/2014-01/msg00375.html
>
Thanks for your reminder. I will add an entry for riscv toolchain at
the end of libc-abis
next prev parent reply other threads:[~2020-07-17 2:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 8:26 Vincent Chen
2020-07-09 8:42 ` Andreas Schwab
2020-07-17 2:50 ` Vincent Chen
2020-07-09 16:40 ` Joseph Myers
2020-07-17 2:53 ` Vincent Chen [this message]
2020-07-10 23:16 ` Jim Wilson
2020-07-17 3:05 ` Vincent Chen
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='CABvJ_xhnKpQznneD+9ONHXOkvEGGVwi=qRBJ_oQ35mooSzztGQ@mail.gmail.com' \
--to=vincent.chen@sifive.com \
--cc=darius@bluespec.com \
--cc=dj@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=palmer@dabbelt.com \
/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).