This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC 2.0] Implementing hwcap2
- From: Roland McGrath <roland at hack dot frob dot com>
- To: "Ryan S. Arnold" <rsa at us dot ibm dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Mon, 8 Apr 2013 15:05:07 -0700 (PDT)
- Subject: Re: [RFC 2.0] Implementing hwcap2
- References: <20130328 dot 173934 dot 1310725546115298719 dot davem at davemloft dot net> <201303281931 dot 43830 dot vapier at gentoo dot org> <20130328234033 dot 9197A2C0A7 at topped-with-meat dot com> <20130328 dot 201048 dot 1654197573467873843 dot davem at davemloft dot net>
The calling convention for IFUNC resolvers is machine-specific.
Thus, it's up to each machine maintainer to decide what it should be
for his machine. Given how rare IFUNC use still is, I'd say it's
also up to each machine maintainer to decide whether or not an
incompatible change to the convention is acceptable at this stage.
It might be nice if these conventions were unified, but to get there
from the status quo would require consensus among all the maintainers
for machines that now support IFUNC at all.
Ryan, I think what you need to do is go back and split your change up
into the generic and machine-specific parts. First, we can review
the generic changes and come to a resolution on those parts. (I
reviewed them before, but since then I've concluded that there is
some muddlation about what it means for 64-bit configurations and I
think we should discuss it more.) Once that's done, you can send a
separate machine-specific change for each machine and hash out the
IFUNC resolver calling convention with that machine's maintainer(s).
Thanks,
Roland