public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: marcus@jet.franken.de
To: gcc-gnats@gcc.gnu.org
Subject: java/8310: iCE in tree_low_cst on (slightly illegal) java input
Date: Tue, 22 Oct 2002 12:26:00 -0000	[thread overview]
Message-ID: <20021022192338.10846.qmail@sources.redhat.com> (raw)


>Number:         8310
>Category:       java
>Synopsis:       iCE in tree_low_cst on (slightly illegal) java input
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Oct 22 12:26:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     marcus@jet.franken.de
>Release:        gcc version 3.3 20021020
>Organization:
>Environment:
suse 8.1, glibc 2.2.5
>Description:
On i686-pc-linux-gnu, the attached testcase ices with:

gcc -O2 -c x.java
x.java: In class `x':
x.java: In method `x.f(byte)':
x.java:5: Internal compiler error in tree_low_cst, at tree.c:3484

reducing the testcase leads to successful compile.

(It might be slightly illegal code though.)
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-java; name="x.java"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="x.java"

cHVibGljIGNsYXNzIHggewogIHB1YmxpYyBpbnQgZihieXRlIGIpCiAgewogICAgYj0oYnl0ZSko
KGludCliLTI1Nik7CiAgICBzd2l0Y2ggKGIpIHsKICAgIGNhc2UgKGJ5dGUpMjU1OiBicmVhazsK
ICAgIGNhc2UgKGJ5dGUpMjUxOiBicmVhazsKICAgIGNhc2UgKGJ5dGUpMjUyOiBicmVhazsKICAg
IGNhc2UgKGJ5dGUpMjUzOiByZXR1cm4gMTsKICAgIGNhc2UgKGJ5dGUpMjU0OiBicmVhazsKICAg
IH0KICAgIHJldHVybiAwOwogIH0KfQo=


             reply	other threads:[~2002-10-22 19:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22 12:26 marcus [this message]
2003-05-12 20:36 Dara Hazeghi

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=20021022192338.10846.qmail@sources.redhat.com \
    --to=marcus@jet.franken.de \
    --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).