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] |
It's the libgcj_tools_la-tools which gets built twice for each architecture and its build seems to always fire off last and takes a few minutes for each compilation."Jeff" == Jeff Law<law@redhat.com> writes:Jeff> Building libjava (at least for me) is primarily painful due to 2 files Jeff> (the names escape me) and the rather poor coarse level parallelism Jeff> (can't build the 32bit and 64bit multilibs in parallel for example).
Jeff> Has anyone looked at fixing the build machinery for libjava to make it Jeff> more sensible?
Nope. AFAIK it is already as parallelized as possible, but it has been a while since I looked at it.
I thought the really bad file (HTML_401F.java, IIRC) had some functions split up so that it wasn't so evil any more.
Yea, I suspect the way multilibs are handled is far from ideal from a parallel make standpoint. Fixing the underlying multilib goop may be ugly, but probably would have a nice benefit across the various runtime libraries we utilize.The multilib thing sounds like a top-level problem of some kind. At least, I don't recall that libjava does anything special here.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |