This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: PATCH: Check GLIBC_IFUNC to enable/disable ifunc features
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, Siddhesh Poyarekar <sid at reserved-bit dot com>
- Date: Thu, 30 Jun 2016 04:35:44 -0700
- Subject: Re: PATCH: Check GLIBC_IFUNC to enable/disable ifunc features
- Authentication-results: sourceware.org; auth=none
- References: <CAMe9rOq1+_rMbs1mt3=Md=Wx=7ZxUbD+BhOx-qrO5TBRBrRLww at mail dot gmail dot com> <20160630013716 dot GY4685 at vapier dot lan> <CAMe9rOrgshV6t5quE01r_oc91ps0JJ7fYfAC=MuQOs96qNv1uQ at mail dot gmail dot com> <20160630043022 dot GA4685 at vapier dot lan>
On Wed, Jun 29, 2016 at 9:30 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> On 29 Jun 2016 19:56, H.J. Lu wrote:
>> On Wed, Jun 29, 2016 at 6:37 PM, Mike Frysinger <vapier@gentoo.org> wrote:
>> > On 29 Jun 2016 11:15, H.J. Lu wrote:
>> >> On Tue, Jun 28, 2016 at 7:28 PM, Mike Frysinger <vapier@gentoo.org> wrote:
>> >> > should have a comment or two mentioning why you need to code all of
>> >> > these things ad-hoc
>> >> >
>> >> > also needs a manual update
>> >>
>> >> I am not sure if it needs manual update. I consider it more for glibc
>> >> developers than for normal end users.
>> >
>> > it needs documenting somewhere beyond the commit message. i guess we
>> > don't have a "hacking" page somewhere, so at least the comment in the
>> > source file will have to do.
>>
>> It is more than just normal "hacking". You need to look at all multiarch
>> implementations when experimenting and their behavior can change over
>> time. It is more a tool for multiarch developers. It shouldn't be used by
>> majority of end users.
>
> "hacking" documents shouldn't be read by the majority of end users either.
> throwing it in the wiki under a hacking/ifunc page sounds fine.
> -mike
We can point it to source codes.
--
H.J.