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++/36023]  New: [4.1/4.3/4.4 regression] ICE with cast to variable-sized object
Date: Wed, 23 Apr 2008 06:44:00 -0000	[thread overview]
Message-ID: <bug-36023-1771@http.gcc.gnu.org/bugzilla/> (raw)

The following code snippet triggers an ICE on the 4.3 branch and mainline:

========================
void foo(int i)
{
  (int [i]) { 1 };
}
========================

bug.cc: In function 'void foo(int)':
bug.cc:3: internal compiler error: in tree_low_cst, at tree.c:4879
Please submit a full bug report, [etc.]

This is a regression on the 4.3 branch as 4.3.0 is not affected.
The ICE also appears in GCC 4.1.x, but is is not present in GCC 4.2.x.


-- 
           Summary: [4.1/4.3/4.4 regression] ICE with cast to variable-sized
                    object
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Keywords: ice-on-invalid-code, 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=36023


             reply	other threads:[~2008-04-23  6:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23  6:44 reichelt at gcc dot gnu dot org [this message]
2008-04-23  6:44 ` [Bug c++/36023] " reichelt at gcc dot gnu dot org
2008-04-28  4:33 ` mmitchel at gcc dot gnu dot org
2008-04-28 17:51 ` jakub at gcc dot gnu dot org
2008-05-21 19:57 ` jakub at gcc dot gnu dot org
2008-05-21 19:58 ` jakub at gcc dot gnu dot org
2008-05-21 19:59 ` jakub at gcc dot gnu dot org
2008-05-21 20:00 ` jakub 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-36023-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).