From: Anthony Green <green@redhat.com>
To: Gary Benson <gbenson@redhat.com>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: ant+ecj
Date: Thu, 27 May 2004 01:25:00 -0000 [thread overview]
Message-ID: <1085621089.9299.133.camel@localhost.localdomain> (raw)
In-Reply-To: <20040526144915@3d3eefe324b0b614c23323a941137724>
On Wed, 2004-05-26 at 07:49, Gary Benson wrote:
> Anthony Green wrote:
> > ecj has been in rhug for some time now. Running it in-process [in
> > ant] as the default java compiler makes for a wicked fast build
> > system.
>
> Jesus, you weren't kidding! It's so fast compared to RHUG builds that
> I didn't think it had done anything until I checked!
I've benchmarked it against jikes in the past as a stand alone compiler,
and this is faster.
So I think it's fair to say that for ant based builds, we'll compare
even more favorably against ant+jikes since we won't spawn processes.
AG
--
Anthony Green <green@redhat.com>
Red Hat, Inc.
prev parent reply other threads:[~2004-05-27 1:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-16 5:53 ant+ecj Anthony Green
2004-05-24 10:35 ` ant+ecj Gary Benson
2004-05-26 16:01 ` ant+ecj Gary Benson
2004-05-27 1:25 ` Anthony Green [this message]
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=1085621089.9299.133.camel@localhost.localdomain \
--to=green@redhat.com \
--cc=gbenson@redhat.com \
--cc=rhug-rhats@sources.redhat.com \
/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).