public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "emailwastefilter-bugzillagccorg at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/22551] [4.0/4.1 Regression] [ICE] in tree_low_cst, at tree.c:3843
Date: Mon, 18 Jul 2005 18:05:00 -0000 [thread overview]
Message-ID: <20050718180349.19867.qmail@sourceware.org> (raw)
In-Reply-To: <20050718171941.22551.emailwastefilter-bugzillagccorg@yahoo.com>
------- Additional Comments From emailwastefilter-bugzillagccorg at yahoo dot com 2005-07-18 18:03 -------
(In reply to comment #2)
> Hmm, 0x80000000+1 overflows which is invalid for constant expressions and
really should be
> rejected.
The warnings seem on the money, but they should not cause the compiler to crash,
right?
The original code used 0xFFFE0000 in place of 0x80000000 and had around 26
warning messages before it crashed. If there are only 4 warning messages, then
the compiler completes without crashing. Starting with 0x80000000 - 2 lets the
compiler complete, as does commenting out one of the case statements.
Several obivous ways around this code are to use an enum, an unsigned int, or an
if-else if cascasde. These all result in no warnings, the first two justly, the
last I'm not so sure.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22551
next prev parent reply other threads:[~2005-07-18 18:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 17:22 [Bug c++/22551] New: " emailwastefilter-bugzillagccorg at yahoo dot com
2005-07-18 17:27 ` [Bug c++/22551] " emailwastefilter-bugzillagccorg at yahoo dot com
2005-07-18 17:41 ` [Bug c++/22551] [4.0/4.1 Regression] " pinskia at gcc dot gnu dot org
2005-07-18 18:05 ` emailwastefilter-bugzillagccorg at yahoo dot com [this message]
2005-07-18 18:07 ` pinskia at gcc dot gnu dot org
2005-09-10 3:17 ` pinskia at gcc dot gnu dot org
2005-09-12 20:48 ` pinskia at gcc dot gnu dot org
2005-09-27 16:24 ` mmitchel at gcc dot gnu dot org
[not found] <bug-22551-11017@http.gcc.gnu.org/bugzilla/>
2005-10-13 11:52 ` nathan at gcc dot gnu dot org
2005-10-14 12:55 ` cvs-commit at gcc dot gnu dot org
2005-10-14 13:00 ` nathan at gcc dot gnu dot org
2005-10-14 13:01 ` cvs-commit at gcc dot gnu dot org
2005-10-16 9:02 ` nathan at gcc dot gnu dot org
2005-10-16 22:07 ` mmitchel at gcc dot gnu dot org
2005-10-17 8:36 ` nathan at gcc dot gnu dot org
2005-10-17 13:54 ` cvs-commit at gcc dot gnu dot org
2005-10-17 13:57 ` cvs-commit at gcc dot gnu dot org
2005-10-17 13:57 ` nathan at gcc dot gnu dot org
2005-10-19 12:48 ` cvs-commit at gcc dot gnu dot org
2005-10-19 12:50 ` nathan 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=20050718180349.19867.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).