public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/14635] New: nan functions should not be C90 built-ins
Date: Thu, 18 Mar 2004 16:40:00 -0000 [thread overview]
Message-ID: <20040318163951.14635.jsm28@gcc.gnu.org> (raw)
The built-in functions nan, nanf, nanl, nans, nansf, nansl are not
part of C90; they should not be built in in C90 mode. nans* are
not in C99 either. Furthermore, the treatment of these as constant
expressions in some cases means they shouldn't be built in at all
with the names nan*, only with the __builtin_nan* names. This accords
with the manual, which only documents them with those names and not as
nan*.
A patch is in testing; this PR is to record the issue as a regression
in 3.4 relative to 3.2.x and earlier. (The same bug is in 3.3.3 but
would need a separate patch there as builtins.def has been reorganised
since then.)
--
Summary: nan functions should not be C90 built-ins
Product: gcc
Version: 3.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jsm28 at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org,mark at codesourcery dot
com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14635
next reply other threads:[~2004-03-18 16:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 16:40 jsm28 at gcc dot gnu dot org [this message]
2004-03-18 17:04 ` [Bug c/14635] [3.3/3.4/3.5 Regression] " pinskia at gcc dot gnu dot org
2004-03-20 0:07 ` mmitchel at gcc dot gnu dot org
2004-03-20 0:13 ` jsm at polyomino dot org dot uk
2004-03-20 2:05 ` mark at codesourcery dot com
2004-03-20 3:47 ` gdr at integrable-solutions dot net
2004-03-20 10:19 ` cvs-commit at gcc dot gnu dot org
2004-03-20 10:22 ` cvs-commit at gcc dot gnu dot org
2004-06-11 22:22 ` [Bug c/14635] [3.3 " pinskia at gcc dot gnu dot org
2004-09-28 13:28 ` gdr at gcc dot gnu dot org
2004-11-26 23:07 ` neroden at gcc dot gnu dot org
2004-11-26 23:12 ` joseph at codesourcery dot com
2005-04-30 14:36 ` gdr at gcc dot gnu 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=20040318163951.14635.jsm28@gcc.gnu.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).