public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Anthony Green <green@localhost.localdomain>
To: gcc-gnats@gcc.gnu.org
Subject: java/9170: gcj regression: ICE in walk_tree, at tree-inline.c:1692
Date: Sat, 04 Jan 2003 12:06:00 -0000	[thread overview]
Message-ID: <200301041206.h04C6B7F002087@localhost.localdomain> (raw)


>Number:         9170
>Category:       java
>Synopsis:       gcj regression: ICE in walk_tree, at tree-inline.c:1692
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Sat Jan 04 04:06:00 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Anthony Green
>Release:        3.3 20030102 (prerelease)
>Organization:
>Environment:
System: Linux escape 2.4.18-18.8.0 #1 Thu Nov 14 00:10:29 EST 2002 i686 i686 i386 GNU/Linux
Architecture: i686

	
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc/configure --prefix=/home/green/net/i --enable-threads --enable-languages=c,c++,java
>Description:

	I stumbled across a gcj problem that was previously reported
as PR 8138.  However, in running the test case from 8138, I found a
completely different problem....

src/org/xwt/HTTP.java:610: internal compiler error: in walk_tree, at tree-inline.c:1692

	This is a regression, as older versions of gcj can build this code.

>How-To-Repeat:
	Follow the How-To-Repeat steps from PR 8138.
>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-01-04 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-04 12:06 Anthony Green [this message]
2003-01-08 12:26 Andrew Haley
2003-01-25  0:50 jbuck
2003-01-25  1:16 Tom Tromey
2003-01-25 11:54 aph
2003-01-29 11:33 aph

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=200301041206.h04C6B7F002087@localhost.localdomain \
    --to=green@localhost.localdomain \
    --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).