This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/16787] NAN constant "(0.0/0.0)" cannot be compiled by Tru64 cc
- From: "scott dot bailey at eds dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 28 Jul 2004 14:12:14 -0000
- Subject: [Bug bootstrap/16787] NAN constant "(0.0/0.0)" cannot be compiled by Tru64 cc
- References: <20040727192305.16787.scott.bailey@eds.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From scott dot bailey at eds dot com 2004-07-28 14:12 -------
Subject: RE: NAN constant "(0.0/0.0)" cannot be comp
iled by Tru64 cc
>Looks like another bug in a DEC's (Compaq/HP's) compiler.
Yeah, what a pain. It turns out my suggested patch isn't quite good enough,
as much later on in the bootstrap process (I think during the build of the
C++ stuff) the (re-)build of floatformat.c dies again with "DBL_QNAN not
defined"... It appears that Tru64's /usr/include/float.h may be getting
occluded by one or another of the gcc float.h files. (I know I was up past
at least stage 2 of the bootstrap when I went home last night.)
I had earlier tried bootstrapping with my installed gcc 3.3.3 compiler, but
that failed early on with an apparent error in one of the generated
Makefiles and I couldn't even be sure which was at fault, much less what was
triggering the error. So I thought fudging the NAN definition might be
easier... Ha ha ha...
I will try replacing the '#include "float.h"' in my fix with an inline
definition of the two lines or so from float.h that appear to be required to
define DBL_QNAN and report back on my success or lack thereof. It probably
will be tomorrow, my system doesn't exactly build like lightning. :-)
Cheers,
Scott Bailey
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16787