Re: [SH][PATCH] __fpscr_values broken

[Kaz Kojima <kkojima at rr dot iij4u dot or dot jp>]

Mike Frysinger <vapier@gentoo.org> wrote:
> is this actually sh4 specific ?  should the symbol actually be in libc rather 
> than libm ?
> 
> there is a bit of history with __fpscr_values that can be found by searching 
> the mailing list ... afaik, this has been broken since before glibc-2.3.2 ...

No, it was broken before glibc-2.3.2 era.  Before that era,
every shared libraries may have their own local __fpscr_values
given by libgcc.  It's wrong because __fpscr_values should be
the unique object in the executable image.  We put __fpscr_values
in the crt object to avoid the issue.  Unfortunately it causes
the link time error with z-defs option when building libc/libm.
Pragmatically, putting it in libc.so is not problem because
almost all programs would link with libc.  Though we decided
not to do so and it'd be too late to change it.

Regards,
	kaz