public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Franz.Sirl-kernel@lauterbach.com
To: gcc-gnats@gcc.gnu.org
Cc: Mark Mitchell <mark@codesourcery.com>
Subject: optimization/6093: ICE in merge_if_block, at ifcvt.c:1870
Date: Fri, 29 Mar 2002 09:26:00 -0000	[thread overview]
Message-ID: <20020329171617.12716.qmail@sources.redhat.com> (raw)


>Number:         6093
>Category:       optimization
>Synopsis:       ICE in merge_if_block, at ifcvt.c:1870
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Fri Mar 29 09:26:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Franz.Sirl-kernel@lauterbach.com
>Release:        gcc version 3.1 20020328 (prerelease)
>Organization:
>Environment:
powerpc-linux-gnu
binutils-2.11.93.0.2-9
glibc-2.2.5-27a_31
>Description:
gcc/testsuite/gcc.dg/20000906-1.c ICE's on powerpc-linux-gnu if
compiled with -O1 or higher. This is a regression from gcc-3.0.4,
but no "showstopper" (not seen in the wild yet), so it's OK for
me if fixing the ICE is deferred until gcc-3.1.1 or later.
>How-To-Repeat:
[fsirl@enzo:~]$ gcc -O1 -c /cvsx/gcc31/gcc/testsuite/gcc.dg/20000906-1.c
/cvsx/gcc31/gcc/testsuite/gcc.dg/20000906-1.c: In function `foo':
/cvsx/gcc31/gcc/testsuite/gcc.dg/20000906-1.c:60: Internal compiler error in merge_if_block, at ifcvt.c:1870
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-03-29 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-29  9:26 Franz.Sirl-kernel [this message]
2002-04-18 21:02 rth

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=20020329171617.12716.qmail@sources.redhat.com \
    --to=franz.sirl-kernel@lauterbach.com \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    /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).