public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "scott dot bailey at eds dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/16787] New: NAN constant "(0.0/0.0)" cannot be compiled by Tru64 cc Date: Tue, 27 Jul 2004 19:23:00 -0000 [thread overview] Message-ID: <20040727192305.16787.scott.bailey@eds.com> (raw) Bootstrap of gcc-3.4.1 fails using cc compiler under Tru64 V5.1B, trying to compile libiberty/floatformat.c. The macro NAN is defined as the constant expression "(0.0 / 0.0)", which is not compilable by HP's cc compiler. The following kludgy patch was sufficient to get me past the problem, but is totally inappropriate "as-is" for a generic fix. :-) *** libiberty/floatformat.c Wed Dec 3 13:36:50 2003 --- libiberty/floatformat.c Tue Jul 27 15:09:15 2004 *************** *** 43,49 **** #endif #ifndef NAN ! #define NAN (0.0 / 0.0) #endif static unsigned long get_field PARAMS ((const unsigned char *, --- 43,50 ---- #endif #ifndef NAN ! #include "float.h" ! #define NAN DBL_QNAN #endif static unsigned long get_field PARAMS ((const unsigned char *, -- Summary: NAN constant "(0.0/0.0)" cannot be compiled by Tru64 cc Product: gcc Version: 3.4.1 Status: UNCONFIRMED Severity: minor Priority: P3 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: scott dot bailey at eds dot com CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: alphaev56-dec-osf5.1 GCC host triplet: alphaev56-dec-osf5.1 GCC target triplet: alphaev56-dec-osf5.1 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16787
next reply other threads:[~2004-07-27 19:23 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-27 19:23 scott dot bailey at eds dot com [this message] 2004-07-28 6:07 ` [Bug bootstrap/16787] " pinskia at gcc dot gnu dot org 2004-07-28 14:12 ` scott dot bailey at eds dot com 2004-07-28 19:30 ` scott dot bailey at eds dot com 2004-07-29 11:44 ` falk at debian dot org 2004-07-29 14:02 ` scott dot bailey at eds dot com 2004-07-30 14:54 ` scott dot bailey at eds dot com 2004-09-02 13:54 ` pinskia at gcc dot gnu dot org 2004-09-09 17:04 ` pinskia at gcc dot gnu dot org 2005-02-14 10:27 ` w dot northcott at unsw dot edu dot au 2005-05-15 1:08 ` pinskia at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20040727192305.16787.scott.bailey@eds.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).