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 14:07:00 -0000	[thread overview]
Message-ID: <20101024140700.-UQx6pUFN8NTB5Vqjo5xzBIBkySQ_JR055Qs4ZC08_w@z> (raw)
In-Reply-To: <bug-46155-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2010-10-24 14:07:25 UTC ---
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 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.


  parent reply	other threads:[~2010-10-24 14:07 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 [this message]
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
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=20101024140700.-UQx6pUFN8NTB5Vqjo5xzBIBkySQ_JR055Qs4ZC08_w@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).