public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/16643] New: [3.4 Regression] verify_local_live_at_start ICE after crossjumping & cfgcleanup
Date: Tue, 20 Jul 2004 13:03:00 -0000	[thread overview]
Message-ID: <20040720130304.16643.rsandifo@gcc.gnu.org> (raw)

Compiling:

void f (int a, int b, int c, int d, int e, int *f)
{
  if (a == 0)
    if (b == 0)
      if (c == 0)
	if (d == 0)
	  {
	    *f += e;
	    return;
	  }
  *f += e;
  return;
}

with "mips64-elf-gcc -O2" gives:

/tmp/foo.c: In function `f':
/tmp/foo.c:13: internal compiler error: in verify_local_live_at_start, at flow.c:546
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.

Same thing for other mips targets, like mips64-linux-gnu.  The problem
is really target-independent: cleanup_cfg (CLEANUP_CFGLAYOUT), called
from within bbreorder, is deleting uses of registers and not updating
liveness information.  This in turn seems to expose a problem with
try_simplify_condjump() not updating the forwarder block flags.

Testing a couple of fixes now.

-- 
           Summary: [3.4 Regression] verify_local_live_at_start ICE after
                    crossjumping & cfgcleanup
           Product: gcc
           Version: 3.4.1
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P2
         Component: rtl-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: rsandifo at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
GCC target triplet: mips64-elf


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16643


             reply	other threads:[~2004-07-20 13:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-20 13:03 rsandifo at gcc dot gnu dot org [this message]
2004-07-20 13:03 ` [Bug rtl-optimization/16643] " rsandifo at gcc dot gnu dot org
2004-07-20 13:22 ` rsandifo at gcc dot gnu dot org
2004-07-20 14:06 ` [Bug rtl-optimization/16643] [3.4/3.5 " pinskia at gcc dot gnu dot org
2004-07-26 14:34 ` cvs-commit at gcc dot gnu dot org
2004-07-26 14:42 ` cvs-commit at gcc dot gnu dot org
2004-07-26 14:44 ` rsandifo 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=20040720130304.16643.rsandifo@gcc.gnu.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).