This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: [gcj-eclipse-merge-branch] MinGW ecj: Cross-built ecjx?! (was Re: ecj branch)
- From: Tom Tromey <tromey at redhat dot com>
- To: gnustuff at thisiscool dot com
- Cc: java at gcc dot gnu dot org
- Date: 05 Dec 2006 12:25:06 -0700
- Subject: Re: [gcj-eclipse-merge-branch] MinGW ecj: Cross-built ecjx?! (was Re: ecj branch)
- References: <HGSRKIPNSFE62IE3VXRNYT72ECB8CA.4575c708@d9300>
- Reply-to: tromey at redhat dot com
>>>>> "Mohan" == Mohan Embar <gnustuff@thisiscool.com> writes:
>> ecj1 (which is what ecjx is called when it is installed) is sort of
>> like cpp, back in the days when we had a separate preprocessor. gcj
>> will invoke ecj1 first, then pass its (class file) output to jc1 for
>> further compilation.
Mohan> So to paraphrase: ecj1 is target independent and doesn't
Mohan> produce object code?
Correct. ecj1 is pure java and it translates .java to .class.
Note that by this I mean that the bytecode bits of ecj1 are platform
independent. Of course to run the thing you may need to compile it.
And the "ecjx" we compile and then install is a real executable,
though a somewhat funny one... it is more like a "gij" with the main
class name compiled in.
Tom