This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: using distcc to speed up GCC bootstraps
>>>>> "Alexandre" == Alexandre Oliva <aoliva@redhat.com> writes:
>> Basically it seems to me all you need to do is ship across the referenced
>> source and the command line -- for java that's all you need
Alexandre> Not in the distcc case. In our particular case, because of
Alexandre> the requirement to have access to the build tree in order
Alexandre> to run the compiler, we probably also have access to the
Alexandre> libjava build tree. But we don't necessarily have access
Alexandre> to the source tree.
I think having the build tree and one .java file available should be
sufficient for compiling .java -> .o in libgcj. All the .class files
should be in libgcj.jar at this point, libgcj.spec is in the build tree.
I can't think of anything else we read anything else during a compilation.
Compiling .java -> .class is a different matter. In that case you
need the whole source tree around. I wouldn't be surprised if
compiling Object.java required us to parse 50-60 files.
Tom