public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: janis187@us.ibm.com
To: gcc-gnats@gcc.gnu.org
Subject: middle-end/8306: ICE for bitfield7_y.C in C++ compatibility tests
Date: Mon, 21 Oct 2002 16:46:00 -0000	[thread overview]
Message-ID: <20021021233652.6240.qmail@sources.redhat.com> (raw)


>Number:         8306
>Category:       middle-end
>Synopsis:       ICE for bitfield7_y.C in C++ compatibility tests
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Mon Oct 21 16:46:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Janis Johnson
>Release:        GCC 3.3 20021018 (experimentatal)
>Organization:
>Environment:
powerpc*
>Description:
The testsuite file g++.dg/compat/eh/bitfield7_y.C causes GCC
to ICE for powerpc, arm, and sparc targets (as seen by test
results in the gcc-testresults archive).  These occur with
GCC 3.3 20021018 (experimental).  I don't know if the ICE
occurs with earlier versions of GCC; perhaps someone with
ready access to earlier versions for those targets can try
the test case with them.

The ICE is in simplify_gen_subreg, at simplify-rtx.c:2681.

See David Edelsohn's analysis at
http://gcc.gnu.org/ml/gcc/2002-10/msg01133.html.
>How-To-Repeat:
Compile gcc/testsuite/g++.dg/compat/eh/bitfield7_y.C with
target of powerpc, sparc, or arm.
>Fix:

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


             reply	other threads:[~2002-10-21 23:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21 16:46 janis187 [this message]
2002-12-20  7:39 ehrhardt

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=20021021233652.6240.qmail@sources.redhat.com \
    --to=janis187@us.ibm.com \
    --cc=gcc-gnats@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).