This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Dacapo Benchmark suite
- From: Tom Tromey <tromey at redhat dot com>
- To: "Eric Bodden" <eric dot bodden at mail dot mcgill dot ca>
- Cc: "Delvin Defoe" <defoe at wustl dot edu>, java at gcc dot gnu dot org
- Date: Fri, 04 May 2007 21:34:55 -0600
- Subject: Re: Dacapo Benchmark suite
- References: <e650cf0e0705041332rab5efa2x52ca40da28dc2cc9@mail.gmail.com> <804e3c660705041340u1a6ad998tf358645dbc3b2608@mail.gmail.com>
- Reply-to: tromey at redhat dot com
>>>>> "Eric" == Eric Bodden <eric.bodden@mail.mcgill.ca> writes:
Eric> Hmm, I am not sure whether I can help you with that. Usually we here
Eric> first compile DaCapo using standard javac and then optimize the
Eric> produced bytecode. In general, DaCapo is built using several ant
Eric> scripts. That might make your job quite hard, actually.
Eric> Does gcj use the very same command line parameters as javac? Or does
Eric> it even come with its own ant task? Then you could probably make the
Eric> ant script believe that your gcj is actually just some version of
Eric> javac...
Probably the simplest thing is to just go ahead and compile with
whatever javac you have, then compile the jars to object code.
ant does have a gcj adapter, but if you are using the svn trunk you
might as well use the ecj adapter instead. If you're on a recent free
OS, Fedora springs to mind :), then javac points to ecj already and
ant is set up to use it automatically.
Tom