This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: libm error handling
- From: Rich Felker <dalias at aerifal dot cx>
- To: Andreas Schwab <schwab at linux-m68k dot org>
- Cc: Roland McGrath <roland at hack dot frob dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, libc-alpha at sourceware dot org
- Date: Tue, 30 Apr 2013 18:12:30 -0400
- Subject: Re: libm error handling
- References: <Pine dot LNX dot 4 dot 64 dot 1304301628510 dot 21969 at digraph dot polyomino dot org dot uk> <20130430181544 dot GG20323 at brightrain dot aerifal dot cx> <Pine dot LNX dot 4 dot 64 dot 1304301910460 dot 28945 at digraph dot polyomino dot org dot uk> <20130430195734 dot B5AB82C08F at topped-with-meat dot com> <20130430200511 dot GH20323 at brightrain dot aerifal dot cx> <20130430205519 dot C86632C088 at topped-with-meat dot com> <20130430213524 dot GJ20323 at brightrain dot aerifal dot cx> <m2a9of4r15 dot fsf at igel dot home>
On Wed, May 01, 2013 at 12:01:10AM +0200, Andreas Schwab wrote:
> Rich Felker <dalias@aerifal.cx> writes:
>
> > Are you claiming that, at one time, the documented API was that you
> > define _your own_ variable named signgam and lgamma writes into it?
>
> On architectures that use copy relocations the variable will always be
> allocated in the main program, even if it doesn't actually define it.
That's an implementation detail, not part of the language semantics.
Existing binaries with the copy relocation for signgam should not be
broken by changing signgam to a weak alias for __signgam internally.
Rich