This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] powerpc: New feature - HWCAP/HWCAP2 bits in the TCB
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: munroesj at linux dot vnet dot ibm dot com, Alan Modra <amodra at gmail dot com>
- Cc: Rich Felker <dalias at libc dot org>, libc-alpha at sourceware dot org
- Date: Wed, 08 Jul 2015 04:10:29 -0400
- Subject: Re: [PATCH] powerpc: New feature - HWCAP/HWCAP2 bits in the TCB
- Authentication-results: sourceware.org; auth=none
- References: <20150609163835 dot GI17573 at brightrain dot aerifal dot cx> <1435777940 dot 7125 dot 132 dot camel at oc7878010663> <5596C284 dot 9070108 at redhat dot com> <1436145404 dot 10792 dot 46 dot camel at oc7878010663> <20150706021300 dot GU1173 at brightrain dot aerifal dot cx> <1436189206 dot 9162 dot 21 dot camel at oc7878010663> <20150706155219 dot GV1173 at brightrain dot aerifal dot cx> <1436217981 dot 8449 dot 8 dot camel at oc7878010663> <20150706215657 dot GZ1173 at brightrain dot aerifal dot cx> <1436221527 dot 8449 dot 15 dot camel at oc7878010663> <20150707023611 dot GB4321 at bubble dot grove dot modra dot org> <1436238083 dot 8449 dot 53 dot camel at oc7878010663>
On 07/06/2015 11:01 PM, Steven Munroe wrote:
> We can add the symbol reference to detect old GLIBC and but I believe
> that existing GLIBC versioning would catch this anyway.
There is no implicit guarantee. It happens some times that you reference
another symbol that is new enough that it works and your library is
then subsequently dependent on the newer glibc, but there is no guarantee.
To add a guarantee you have to weave into your macros a reference to
a new dummy symbol with the right version.