This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: input line is too long

From: Tom Tromey <tromey at redhat dot com>
To: Andrew Haley <aph at redhat dot com>
Cc: "Erik Poupaert" <erik dot poupaert at chello dot be>, "Dhek Bhun Kho" <bhun at chello dot nl>, <java at gcc dot gnu dot org>
Date: 30 Dec 2002 16:08:58 -0700
Subject: Re: input line is too long
References: <1040504063.15484.5.camel@localhost><POEIJGMGPFPGFHAGKFHAKEFLCDAA.erik.poupaert@chello.be><15879.10479.367705.565830@cuddles.cambridge.redhat.com>
Reply-to: tromey at redhat dot com

>>>>> "Andrew" == Andrew Haley <aph@redhat.com> writes:

>> Another bizar thing: Jikes compiles sources about a 100 times faster than
>> GCJ. Admitted that GCJ does a bit more work, but not a hundred times!

Andrew> I'm surprised at that if the difference is jikes versus gcj -C.

I think I compared jikes and gcj -C a year or so ago.
As I recall they were comparable in performance.
This was nothing scientific, just compiling some random library with
both compilers and `time'.

Tom

Follow-Ups:
- RE: input line is too long
  - From: Erik Poupaert
- Re: input line is too long
  - From: Dhek Bhun Kho

References:
- Re: input line is too long
  - From: Dhek Bhun Kho
- RE: input line is too long
  - From: Erik Poupaert
- RE: input line is too long
  - From: Andrew Haley

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]