public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de
To: bwheadley@earthlink.net, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: c++/8617: [3.2 regression] ICE in merge_blocks_move_predecessor_nojumps, at cfgcleanup.c:650
Date: Fri, 22 Nov 2002 16:08:00 -0000	[thread overview]
Message-ID: <20021118134210.11565.qmail@sources.redhat.com> (raw)

Old Synopsis: Internal compiler error in merge_blocks_move_predecessor_nojumps, at cfgcleanup.c:650
New Synopsis: [3.2 regression] ICE in merge_blocks_move_predecessor_nojumps, at cfgcleanup.c:650

State-Changed-From-To: open->analyzed
State-Changed-By: reichelt
State-Changed-When: Mon Nov 18 05:42:09 2002
State-Changed-Why:
    Confirmed.
    
    
    The bug can be reproduced with the following code snippet:
    
    ------------------snip here------------------
    void foo (int *&p)
    {
        switch (*p)
        {
          case 3: p=0; break;
          case 4: p=0; break;
          case 5: p=0; break;
          case 6: p=0; break;
          case 7: p=0; break;
        }
    }
    ------------------snip here------------------
    
    I get an ICE with gcc-3.2.1-20021111 (compiling with "g++ -O -fPIC -c"):
    
    PR8617.cc: In function `void foo(int*&)':
    PR8617.cc:11: Internal compiler error in merge_blocks_move_predecessor_nojumps, 
       at cfgcleanup.c:650
    Please submit a full bug report, [etc.]
    
    (Checked on i686-pc-linux-gnu and mips-sgi-irix6.5).
    gcc 3.2 and mainline are not affected.
    
    (The bug might be fixed already, see PR 8592.)

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8617


             reply	other threads:[~2002-11-18 13:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-22 16:08 reichelt [this message]
2002-11-22 16:18 sirl

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=20021118134210.11565.qmail@sources.redhat.com \
    --to=reichelt@igpm.rwth-aachen.de \
    --cc=bwheadley@earthlink.net \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).