public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/36912] [4.2/4.3/4.4 regression] ICE with "-frounding-math -g"
Date: Tue, 09 Dec 2008 19:22:00 -0000 [thread overview]
Message-ID: <20081209192026.753.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36912-16507@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from mmitchel at gcc dot gnu dot org 2008-12-09 19:20 -------
With respect to Comment #4: I see no reason for C++ to be different than C in
this respect, and thus I see no reason not to perform the computation at
compile-time.
In general, although some in the committees do not seem to care, users expect C
to be a subset of C++. Certainly, wherever the standards permit us to do so,
we should make GNU C and GNU C++ behave identically; compiling C code as C++
with the same toolset and getting different results leads to user surprise.
--
mmitchel at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36912
next prev parent reply other threads:[~2008-12-09 19:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 21:18 [Bug c++/36912] New: ICE when building " drussel at gmail dot com
2008-07-23 21:21 ` [Bug c++/36912] " pinskia at gcc dot gnu dot org
2008-08-13 20:49 ` [Bug c++/36912] [4.2/4.3/4.4 regression] ICE " reichelt at gcc dot gnu dot org
2008-08-14 8:04 ` jakub at gcc dot gnu dot org
2008-08-14 12:19 ` joseph at codesourcery dot com
2008-08-14 18:13 ` jakub at gcc dot gnu dot org
2008-08-18 16:13 ` sylvain dot pion at sophia dot inria dot fr
2008-08-22 15:00 ` rguenth at gcc dot gnu dot org
2008-12-09 19:22 ` mmitchel at gcc dot gnu dot org [this message]
2008-12-09 20:05 ` sylvain dot pion at sophia dot inria dot fr
2009-03-31 20:57 ` [Bug c++/36912] [4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org
2009-08-04 12:51 ` rguenth at gcc dot gnu dot org
2009-09-20 20:09 ` pinskia at gcc dot gnu dot org
2009-11-04 22:15 ` jason at gcc dot gnu dot org
2009-11-04 23:13 ` jason at gcc dot gnu dot org
2009-11-05 13:12 ` jason at gcc dot gnu dot org
2009-11-05 14:47 ` jason at gcc dot gnu dot org
2009-11-05 16:33 ` jason at gcc dot gnu dot org
2009-11-05 16:34 ` jason 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=20081209192026.753.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).