public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <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 17:50:00 -0000	[thread overview]
Message-ID: <20101024175000.EfdCw6bWfJFLIhQQExf8wVZXVNLIFDjwtirAm3g3X2U@z> (raw)
In-Reply-To: <bug-46155-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2010-10-24 17:50:44 UTC ---
On Sun, 24 Oct 2010, david.kirkby at onetel dot net wrote:

> > > I don't have a copy of the C standard. Is there one publicly available? In your
> > > opinion, are IBM wrong to define fprnd_t in /usr/include/float.h? AIX 5.3 is a
> > > POSIX certified operating system.
> > 
> > http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdf
> 
> Thank you. Do you happen to have one for the C++ standards too? 

No.

> Solaris 10 was only introduced in 2005, so Solaris 9 is not that old. To my
> knowledge Cygwin does not support C99, though I know the GSL builds on Cygwin. 

I think cygwin does have the fenv.h interfaces.

What is meant by "supporting" C99 is very complicated and it is likely to 
involve (if conscientious) complicated lists of caveats about the state of 
support of optional features, issues of interpretation of the standard, 
and what depends on different parts of the implementation (compiler, 
library, OS).  In this case you just need library interfaces that are easy 
to implement for any OS that has any of the alternative interfaces GSL 
sometimes uses.

> > It appears that GSL has code that uses the C99 interfaces (fp-gnuc99.c).  
> 
> I'm a bit puzzled by that. Perhaps it only uses that when it knows the compiler
> supports C99. 

That would be very silly, given that "supports C99" is a very complicated 
matter not a binary yes/no configure test.  For use of a particular 
library feature it should test for that library feature.  Not for support 
of \uNNNNNNNN extended characters in identifiers or any other random 
compiler feature.  And there's no reason for it to compare about other 
details of compiler Annex F support any more for using the C99 interfaces 
than for any of the other interfaces it uses.

What doesn't make sense to me is that GSL has the C99 interfaces as the 
*last* of a series of alternatives, so always preferring pre-standard 
OS-specific interfaces where both are available.  The sensible thing to do 
would be to prefer standard interfaces where available.


  parent reply	other threads:[~2010-10-24 17:50 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 [this message]
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
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=20101024175000.EfdCw6bWfJFLIhQQExf8wVZXVNLIFDjwtirAm3g3X2U@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).