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: Sun, 24 Oct 2010 19:47:00 -0000	[thread overview]
Message-ID: <20101024194700.n_X65elK-7R_zs2ll8gfGFb8f6UuW8JtwJgb5JqGG04@z> (raw)
In-Reply-To: <bug-46155-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46155

--- Comment #11 from Kalle Olavi Niemitalo <kon at iki dot fi> 2010-10-24 19:47:27 UTC ---
(In reply to comment #7)
> In your opinion, are IBM wrong to define fprnd_t in /usr/include/float.h?

IBM's definition of fprnd_t in <float.h> is within #ifdef _ALL_SOURCE.  I
presume _ALL_SOURCE is not defined when IBM's compiler is used in ISO C
conforming mode.  AFAIK, adding non-standard definitions to standard header
files in non-conforming modes is a common practice.

The <float.h> that GCC installed on AIX is identical to gcc/ginclude/float.h in
the GCC 4.2.4 sources.  I can understand if GCC developers don't want to
introduce OS-specific sections in it.


  parent reply	other threads:[~2010-10-24 19:47 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 [this message]
2010-10-26 17:59 ` david.kirkby at onetel dot net
2010-11-18  8:30 ` kon at iki dot fi
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=20101024194700.n_X65elK-7R_zs2ll8gfGFb8f6UuW8JtwJgb5JqGG04@z \
    --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: link
Be 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).