public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/27722] New: [4.0/4.1/4.2 regression] ICE incrementing an array
Date: Mon, 22 May 2006 13:34:00 -0000 [thread overview]
Message-ID: <bug-27722-1771@http.gcc.gnu.org/bugzilla/> (raw)
The C++ frontend crashes since GCC 4.0.3 on the following invalid code
snippet:
=================================
void foo()
{
const int x[] = 0;
++x;
}
=================================
bug.cc: In function 'void foo()':
bug.cc:3: error: initializer fails to determine size of 'x'
bug.cc:3: error: cannot convert 'int' to 'const int [1]' in initialization
bug.cc:4: internal compiler error: tree check: expected class 'type', have
'exceptional' (error_mark) in get_unwidened, at tree.c:5322
Please submit a full bug report, [etc.]
--
Summary: [4.0/4.1/4.2 regression] ICE incrementing an array
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Keywords: ice-on-invalid-code, error-recovery, monitored
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: reichelt at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27722
next reply other threads:[~2006-05-22 13:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 13:34 reichelt at gcc dot gnu dot org [this message]
2006-05-22 13:55 ` [Bug c++/27722] " pinskia at gcc dot gnu dot org
2006-05-26 14:56 ` bangerth at dealii dot org
2006-06-04 19:21 ` mmitchel at gcc dot gnu dot org
2006-06-05 2:52 ` mmitchel at gcc dot gnu dot org
2006-06-05 2:53 ` mmitchel at gcc dot gnu dot org
2006-06-05 3:08 ` [Bug c++/27722] [4.0 " mmitchel at gcc dot gnu dot org
2006-06-06 14:26 ` reichelt at gcc dot gnu dot org
2007-01-31 23:16 ` reichelt 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=bug-27722-1771@http.gcc.gnu.org/bugzilla/ \
--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).