public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "casevh at comcast dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/19933] New: Problem with define of HUGE_VAL in math_c99. Date: Sun, 13 Feb 2005 18:17:00 -0000 [thread overview] Message-ID: <20050213054900.19933.casevh@comcast.net> (raw) Python does not compile on Solaris 10 x86 GA. The problem exists with gcc-3.4.3 shipped by Sun with Solaris and with a 3.4.4 snapshot I compiled. I reproduced the problem with the following code fragment: #define _XOPEN_SOURCE 1000 #include <math.h> int main() { double f=HUGE_VAL; } Compiler output is: $ gcc hv.c hv.c: In function `main': hv.c:5: error: incompatible types in initialization $ Python defines _XOPEN_SOURCE to be greater than 600 so it triggers the inclusion of math_c99.h. The fix is editing <iso/math_c99.h>. If I copy /usr/include/iso/math_c99.h to <gcc-install-dir>/include/iso/math_c99.h and change the line #define HUGE_VAL __builtin_huge_val to #define HUGE_VAL __builtin_huge_val(). With this change to math_c99.h, Python compiles properly. Should mkheaders/fixincludes deal with this? -- Summary: Problem with define of HUGE_VAL in math_c99. Product: gcc Version: 3.4.4 Status: UNCONFIRMED Severity: normal Priority: P2 Component: preprocessor AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: casevh at comcast dot net CC: gcc-bugs at gcc dot gnu dot org GCC host triplet: i386-pc-solaris2.10 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19933
next reply other threads:[~2005-02-13 5:49 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-13 18:17 casevh at comcast dot net [this message] 2005-02-13 20:13 ` [Bug target/19933] " pinskia at gcc dot gnu dot org 2005-03-04 18:10 ` ebotcazou at gcc dot gnu dot org 2005-03-04 18:12 ` ebotcazou at gcc dot gnu dot org 2005-03-07 6:15 ` casevh at comcast dot net 2005-03-22 20:53 ` jsm28 at gcc dot gnu dot org 2005-04-30 17:10 ` ebotcazou at gcc dot gnu dot org 2005-05-01 12:21 ` ebotcazou at gcc dot gnu dot org 2005-05-01 14:24 ` joseph at codesourcery dot com 2005-05-03 9:49 ` ebotcazou at gcc dot gnu dot org 2005-05-03 10:55 ` joseph at codesourcery dot com 2005-05-03 11:36 ` ebotcazou at gcc dot gnu dot org 2005-05-03 13:02 ` joseph at codesourcery dot com 2005-05-03 14:39 ` ebotcazou at gcc dot gnu dot org 2005-05-03 16:22 ` joseph at codesourcery dot com 2005-05-19 7:06 ` cvs-commit at gcc dot gnu dot org 2005-05-19 7:12 ` cvs-commit at gcc dot gnu dot org 2005-05-19 7:16 ` ebotcazou at gcc dot gnu dot org 2005-05-24 13:39 ` ebotcazou at gcc dot gnu dot org 2005-05-29 20:53 ` cvs-commit at gcc dot gnu dot org 2005-05-29 20:53 ` ebotcazou 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=20050213054900.19933.casevh@comcast.net \ --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).