public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/16178] jc1 ICE: seemingly infinite stack growth while compiling junit or vte
Date: Fri, 25 Jun 2004 09:46:00 -0000	[thread overview]
Message-ID: <20040625094449.25756.qmail@sourceware.org> (raw)
In-Reply-To: <20040624171632.16178.green@redhat.com>


------- Additional Comments From mark at gcc dot gnu dot org  2004-06-25 09:44 -------
My failure disappeared when removing all .class files from the build directory.
(Even though I was building from .java source files). The .class files were
generated by an older jikes. Regenerating the .class files with jikes 1.21
doesn't trigger the bug. I'll try to see if I can reproduce it using an older jikes.

-- 


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


  parent reply	other threads:[~2004-06-25  9:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-24 17:24 [Bug java/16178] New: jc1 ICE: seemingly infinite loop while compiling junit green at redhat dot com
2004-06-24 17:29 ` [Bug java/16178] jc1 ICE: seemingly infinite stack growth " green at redhat dot com
2004-06-25  9:44 ` [Bug java/16178] jc1 ICE: seemingly infinite stack growth while compiling junit or vte mark at gcc dot gnu dot org
2004-06-25  9:46 ` mark at gcc dot gnu dot org [this message]
2004-06-25 11:02 ` rmathew at gcc dot gnu dot org
2004-06-26 20:40 ` mckinlay at redhat dot com
2004-06-26 20:43 ` mckinlay at redhat dot com
2004-06-26 20:53 ` pinskia 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=20040625094449.25756.qmail@sourceware.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).