This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC] Fix float128 IFUNC relocations on ppc64le [BZ #21707]
- From: Florian Weimer <fweimer at redhat dot com>
- To: Carlos O'Donell <carlos at redhat dot com>, Tulio Magno Quites Machado Filho <tuliom at linux dot vnet dot ibm dot com>, libc-alpha at sourceware dot org
- Cc: bergner at vnet dot ibm dot com, joseph at codesourcery dot com, gftg at linux dot vnet dot ibm dot com
- Date: Wed, 5 Jul 2017 21:44:38 +0200
- Subject: Re: [RFC] Fix float128 IFUNC relocations on ppc64le [BZ #21707]
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx09.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx09.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=fweimer at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 38A654ACC7
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 38A654ACC7
- References: <60e4bbfd-186a-e98d-1322-1a4678fcb000@redhat.com> <20170705172315.14358-1-tuliom@linux.vnet.ibm.com> <cd21431e-7201-69c7-2721-07d4c1fb5c45@redhat.com> <0139743d-c15f-9870-b588-1e49c97dd52a@redhat.com>
On 07/05/2017 09:25 PM, Carlos O'Donell wrote:
>>> +# libgcc requires __tcb_parse_hwcap_and_convert_at_platform when built with
>>> +# a binary128 type. That symbol is provided by the loader on dynamically
>>> +# linked executables, forcing to link the loader after libgcc link.
>>> +f128-loader-link = $(as-needed) $(elf-objpfx)ld.so $(no-as-needed)
>> Why doesn't the regular linker invocation take care of this? Will user
>> applications run into the same issue?
> We don't use the regular linker invocation in glibc builds? We have to emulate
> what the actual toolchain would do in this case.
But then we should do this everywhere, and not just for the few tests
that actually need it, right? I assume that's also what the official
linker script does.
Thanks,
Florian