public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kon at iki dot fi" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/46155] Bug with generation of float.h header file on AIX Date: Thu, 18 Nov 2010 08:30:00 -0000 [thread overview] Message-ID: <bug-46155-4-uoeQfsXGsh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46155-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46155 --- Comment #13 from Kalle Olavi Niemitalo <kon at iki dot fi> 2010-11-18 08:10:20 UTC --- Earlier, I thought GCC would eventually have to add some libc-specific definitions to <float.h> anyway, in order to make FLT_ROUNDS call a function in the C library and map the results correctly, and the IBM fprnd_t and function declarations could then be added at the same time; but according to bug 30569, FLT_ROUNDS is supposed to call a built-in function instead. FLT_EVAL_METHOD has a similar "???" comment above it, but C99 says it shall be a "constant expression[s] suitable for use in #if preprocessing directives", so cannot expand to a function call.
next prev parent reply other threads:[~2010-11-18 8:10 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-24 3:48 [Bug c/46155] New: " david.kirkby at onetel dot net 2010-10-24 3:51 ` [Bug c/46155] " david.kirkby at onetel dot net 2010-10-24 3:54 ` david.kirkby at onetel dot net 2010-10-24 4:17 ` david.kirkby at onetel dot net 2010-10-24 4:25 ` david.kirkby at onetel dot net 2010-10-24 14:07 ` joseph at codesourcery dot com 2010-10-24 14:12 ` joseph at codesourcery dot com 2010-10-24 15:06 ` david.kirkby at onetel dot net 2010-10-24 15:21 ` joseph at codesourcery dot com 2010-10-24 16:10 ` david.kirkby at onetel dot net 2010-10-24 17:50 ` joseph at codesourcery dot com 2010-10-24 19:47 ` kon at iki dot fi 2010-10-26 17:59 ` david.kirkby at onetel dot net 2010-11-18 8:30 ` kon at iki dot fi [this message] 2015-02-06 17:32 ` dje at gcc dot gnu.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=bug-46155-4-uoeQfsXGsh@http.gcc.gnu.org/bugzilla/ \ --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).