Subject: Re: strtod
To: Frank van der Linden <email@example.com>
From: J.T. Conklin <firstname.lastname@example.org>
Date: 12/23/1994 14:55:55
> After today's update, there seems to be a bug in strtod. The first
> symptoms were w(1) dumping core and top doing the same thing, later
> cc looped endlessly while recompiling strtod.c itself (presumably
> while writing the assembly output file containing a double constant
> value) This all happened after the new libc had been installed, of course.
> Oh, this is on an i386 system (could be that systems with a different
> byteorder are not seeing this problem).
This is a problem on little endian machines. <machine/endian.h> was
not included, so the endianness test always resulted in a big endian
configuration. I've checked in a fix.