public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Petit-Bianco <apbianco@cygnus.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 09:46:00 -0000	[thread overview]
Message-ID: <20020327174602.27449.qmail@sources.redhat.com> (raw)

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

From: Alexandre Petit-Bianco <apbianco@cygnus.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: Wed, 27 Mar 2002 09:38:51 -0800 (PST)

 shroff@transeda.com writes:
 
 > I have a rather large .java file (21417 lines, 950 static methods) that
 > does not compile with gcj. I let gcj run for about 60 minutes, and it
 > still could not generate the class file. I killed the process after
 > 60 minutes of cpu time. Sun "javac" compiles this file in 90 seconds.
 
 You could try a newer version of gcc, like the 3.1 branch (which builds
 on Solaris 2.8. If the symptoms persist, you can run gdb on the jc1
 invocation and interrupt the process once you suspect it entered the
 generate_bytecode_insns loop and then to step through an iteration to
 find out what's going on.
 
 ./A


             reply	other threads:[~2002-03-27 17:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-27  9:46 Alexandre Petit-Bianco [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 13:36 Tom Tromey
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=20020327174602.27449.qmail@sources.redhat.com \
    --to=apbianco@cygnus.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).