public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincent+libc at vinc17 dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/6981] New: __STDC_IEC_559__ should not be defined unconditionally
Date: Fri, 24 Oct 2008 13:59:00 -0000	[thread overview]
Message-ID: <20081024135805.6981.vincent+libc@vinc17.org> (raw)

__STDC_IEC_559__ is unconditionally defined as 1 in "/usr/include/features.h".
On some platforms, this is incorrect. In particular, if FLT_EVAL_METHOD is 1 or
2, it doesn't make sense to define __STDC_IEC_559__ as this contradicts the
bindings defined in Annex F of the ISO C standard.

I suggest to define __STDC_IEC_559__ only if FLT_EVAL_METHOD is 0 (probably test
__FLT_EVAL_METHOD__).

Even this test would not be sufficient with GCC, as it systematically contracts
expressions (in particular on PowerPC and IA-64, which have a FMA), which is
against the support of Annex F.

-- 
           Summary: __STDC_IEC_559__ should not be defined unconditionally
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: vincent+libc at vinc17 dot org
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=6981

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2008-10-24 13:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 13:59 vincent+libc at vinc17 dot org [this message]
2008-12-16 15:25 ` [Bug libc/6981] " vincent+libc at vinc17 dot 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=20081024135805.6981.vincent+libc@vinc17.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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).