This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: implementing ifunc support
- From: Carlos O'Donell <carlos at redhat dot com>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: Jason Duerstock <jason dot duerstock at gmail dot com>, Binutils <binutils at sourceware dot org>
- Date: Mon, 8 Jul 2019 16:33:19 -0400
- Subject: Re: implementing ifunc support
- References: <CAP5F8cKmAoSE=J2sNaOWPr6Tq6=-e9pxh_0svg+Bgn7HeAmATQ@mail.gmail.com> <21a38996-2aab-25ab-043b-b5a850966fe3@redhat.com> <871rz0mk9r.fsf@oldenburg2.str.redhat.com>
On 7/8/19 2:52 PM, Florian Weimer wrote:
* Carlos O'Donell:
On 7/8/19 11:15 AM, Jason Duerstock wrote:
I'm trying to figure out how to implement ifunc support for ia64, but
I was wondering if there was a more general guide on how to do it.
There is no general "guide" to implementing IFUNC support.
You need gcc, binutils, and gcc support to implement this.
Isn't binutils (linker and assembler) and glibc support sufficient?
Without GCC, the debugging information will be wrong, but we had that
for many years even on the mainstream platforms, so it's obviously not
too bad to be unusable.
Correct, you can get away with a minimum of just binutils and glibc, which
is what we did originally for many architectures.
Modern architectures also want to wire up FMV via IFUNC in gcc, but ia64
which is not releasing new hardware will have limited use for that.
--
Cheers,
Carlos.