public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Diego Novillo <dnovillo@google.com>,
	Ian Lance Taylor <iant@google.com>,
	       Andrew Haley <aph@redhat.com>,
	gcc@gcc.gnu.org, java@gcc.gnu.org,
	       gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Subject: Re: PATCH RFA: Do not build java by default
Date: Tue, 02 Nov 2010 16:25:00 -0000	[thread overview]
Message-ID: <4CD03B55.6080508@redhat.com> (raw)
In-Reply-To: <m3lj5b7n7c.fsf@fleche.redhat.com>

  On 11/02/10 09:35, Tom Tromey wrote:
>>>>>> "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.
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.

> The multilib thing sounds like a top-level problem of some kind.
> At least, I don't recall that libjava does anything special here.
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.

jeff

  reply	other threads:[~2010-11-02 16:25 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31 19:09 Ian Lance Taylor
2010-11-01  8:59 ` Andrew Haley
2010-11-02 10:14   ` Laurent GUERBY
2010-11-02 15:32     ` Tom Tromey
2010-11-01 10:31 ` Dave Korn
2010-11-01 17:36   ` Ian Lance Taylor
2010-11-01 18:16 ` Diego Novillo
2010-11-01 18:58   ` Andrew Haley
2010-11-01 19:35     ` H.J. Lu
2010-11-02  3:39   ` Jeff Law
2010-11-02  3:58     ` H.J. Lu
2010-11-02  8:22     ` Eric Botcazou
2010-11-02 15:31     ` Tom Tromey
2010-11-02 16:25       ` Jeff Law [this message]
2010-11-02  5:12 ` Matthias Klose
2010-11-11 23:20 ` Ian Lance Taylor
2010-11-18  9:23   ` Mark Mitchell
2010-11-18 10:47     ` Andrew Haley
2010-11-18 13:42       ` H.J. Lu
2010-11-18 15:37       ` Mark Mitchell
2010-11-18 16:02         ` Diego Novillo
2010-11-18 15:23     ` Jeff Law
2010-11-18 17:19     ` Ian Lance Taylor
2010-11-18 17:58       ` Dave Korn
2010-11-18 20:53       ` Mark Wielaard
2010-10-31 19:33 Steven Bosscher
2010-10-31 19:47 ` Gerald Pfeifer
2010-11-01  3:48   ` Andrew Pinski
2010-11-01 10:11     ` Dave Korn
2010-11-01  4:06 ` Geert Bosch
2010-11-01  4:30   ` Joern Rennecke
2010-11-01 10:35     ` Geert Bosch
2010-11-01 10:46       ` Joern Rennecke
2010-11-02 10:48         ` Paolo Bonzini
2010-11-02 16:43           ` David Daney
2010-11-01 17:46 ` Tom Tromey
2010-11-01 17:50   ` Andrew Haley

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=4CD03B55.6080508@redhat.com \
    --to=law@redhat.com \
    --cc=aph@redhat.com \
    --cc=dnovillo@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=java-patches@gcc.gnu.org \
    --cc=java@gcc.gnu.org \
    --cc=tromey@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).