glibc 2.1.92 make check results under Linux PPC

[Franz Sirl]

On Mon, 14 Aug 2000, Geoff Keating wrote:
> > From: Andreas Jaeger <aj@suse.de>
> > Date: 14 Aug 2000 07:50:42 +0200
> >
> >  > control word is 0xd4 but should be 0x0.
> >
> > That's easy to track down - the kernel initializes the FPU to a
> > different value than glibc expects.  Check the program, check the
> > value of _FPU_DEFAULT in sysdeps/powerpc/fpu_control.h - and see what
> > the kernel does.  Either of them is at fault.
>
> It looks like it's a kernel bug.  0xd4 is non-IEEE mode with several
> exceptions enabled, you don't want that by default.  The ABI specifies
> that the FPSCR should be cleared at process startup.  Of course, glibc
> could be reading the register wrong...

It's a small bug in the glibc inline assembly. If we want to clobber a 
double-sized memory location, we have to tell it to gcc.

Franz.

	* sysdeps/powerpc/fpu_control.h: Clobber the right amount of memory.