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 middle-end/34245] Missing __builtin_fpclassify
Date: Tue, 27 Nov 2007 15:35:00 -0000	[thread overview]
Message-ID: <20071127153452.1258.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34245-133@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from joseph at codesourcery dot com  2007-11-27 15:34 -------
Subject: Re:   New: Missing __builtin_fpclassify

As previously discussed, this builtin would either need to be used in the 
form

#define fpclassify(x) __builtin_fpclassify(FP_INFINITE, FP_NAN, FP_NORMAL,
FP_SUBNORMAL, FP_ZERO, (x))

or would need GCC to be configured with target-specific information about 
FP_*, since the values of the FP_* macros are not standardized.


-- 


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


  parent reply	other threads:[~2007-11-27 15:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-27 11:46 [Bug middle-end/34245] New: " pcarlini at suse dot de
2007-11-27 12:49 ` [Bug middle-end/34245] " rguenth at gcc dot gnu dot org
2007-11-27 15:35 ` joseph at codesourcery dot com [this message]
2007-11-27 16:01 ` pcarlini at suse dot de
2007-11-27 16:20 ` joseph at codesourcery dot com
     [not found] <bug-34245-16141@http.gcc.gnu.org/bugzilla/>
2009-07-24  9:07 ` paolo dot carlini at oracle dot com

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=20071127153452.1258.qmail@sourceware.org \
    --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).