public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "david.kirkby at onetel dot net" <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 16:10:00 -0000 [thread overview] Message-ID: <20101024161000.gZQ6dprCfRk_o-_miOIIR0OVYs-Kt8ohl4FgqLJO8-Y@z> (raw) In-Reply-To: <bug-46155-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46155 --- Comment #9 from Dr. David Kirkby <david.kirkby at onetel dot net> 2010-10-24 16:10:30 UTC --- (In reply to comment #8) > 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? > > According to > > > > http://www.gnu.org/software/gnulib/manual/html_node/fesetround.html > > > > fegetround() is not very portable, so I doubt the GSL developers would want to > > use that. I've found GSL to be very portable. It seems to build on just about > > anything - except AIX, unless one makes a few changes to a source file. > > All the systems listed there are old systems. ISO C99 was published on 1 > December 1999 - nearly 11 years ago. 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. It should also be noted that gcc is still not fully C99 compliant! http://gcc.gnu.org/c99status.html 11 years after the standard! > 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. > I'd advise using that in preference to all the other pre-C99 OS-specific > interfaces, whenever the C99 interfaces are available, rather than as the > very last alternative. If AIX supports the C99 interfaces, that solves > your problem. AIX 5.3 (released in 2004) fully supports the C99 standard, but earlier AIX versions do not. However, I believe 5.2 supported most of it, so there may be some argument here for using C99 code on AIX. I'm not a GSL developer, so the GSL developers would have to make the final decision on that. But given GSL is very portable, I can imagine the developers might be reluctant to change that. Dave
next prev parent reply other threads:[~2010-10-24 16: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 [this message] 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 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=20101024161000.gZQ6dprCfRk_o-_miOIIR0OVYs-Kt8ohl4FgqLJO8-Y@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: 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).