public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/6071: GCJ does not compile a large (21417 lines) java source file
Date: Wed, 27 Mar 2002 13:36:00 -0000	[thread overview]
Message-ID: <20020327213602.12195.qmail@sources.redhat.com> (raw)

The following reply was made to PR java/6071; it has been noted by GNATS.

From: Tom Tromey <tromey@redhat.com>
To: shroff@transeda.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: java/6071: GCJ does not compile a large (21417 lines) java source file
Date: 27 Mar 2002 15:02:56 -0700

 >>>>> "Saurin" == Saurin B Shroff <shroff@transeda.com> writes:
 
 Saurin> Due to proprietary reason, I cannot supply the java file, but
 Saurin> is there anything else I can do to help you debug the problem?
 
 I suppose you could try to run jc1 in the debugger and track down the
 actual infinite loop (assuming one exists) or other bug.
 
 Saurin> It seems that gcj is stuck in infinite loop in
 Saurin> "generate_bytecode_insns" routine.
 
 It could be.  But note that generate_bytecode_insns is recursive.  So
 it can appear on the stack many times without this indicating a bug.
 
 Tom


             reply	other threads:[~2002-03-27 21:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-27 13:36 Tom Tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-13  6:25 steven
2002-04-26 15:56 Anthony Green
2002-03-28 10:26 Alexandre Petit-Bianco
2002-03-27  9:46 Alexandre Petit-Bianco
2002-03-27  9:36 shroff

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=20020327213602.12195.qmail@sources.redhat.com \
    --to=tromey@redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).