http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46155
--- Comment #7 from Dr. David Kirkby <david.kirkby at onetel dot net> 2010-10-24 15:05:50 UTC --- (In reply to comment #5) > On Sun, 24 Oct 2010, david.kirkby at onetel dot net wrote: > > > On an IBM server running AIX 5.3, 'fprnd_t' is clearly defined in the IBM > > system header file /usr/include/float.h > > > > -bash-4.1$ grep fprnd_t /usr/include/float.h > > typedef unsigned short fprnd_t; > > fprnd_t fp_read_rnd(); > > fprnd_t fp_swap_rnd(); > > fprnd_t fp_read_rnd(void); > > fprnd_t fp_swap_rnd(fprnd_t rnd); > > > > as an unsigned short. > > > > But when gcc is built, it creates several files called 'float.h', but all of > > these lack any references at all to fprnd_t > > Indeed, fprnd_t is not a type that ISO C permits to be declared in > float.h, and nor are the other identifiers in a reserved namespace. So > certainly in ISO C mode GCC's float.h must not include those declarations. 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. Clearly if the C standard says X, Y and Z, and only X, Y and Z should be defined in float.h, then I can see your point. Conversely, if the standard says X, Y and Z must be defined, but other things can be defined, then I would suggest it's a gcc bug. Without knowing the details of the standard, its difficult for me to comment further. I'm sure if I asked IBM they would say it is a gcc bug! > I haven't seen documentation for those functions and types, but they sound > rather like they should be obsoleted by the standard <fenv.h> facilities > such as fegetround and fesetround. 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. Other than manually defining these, do you have a better solution on how to resolve this issue? Dave
