public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: "Peter O'Gorman" <pogma@thewrittenword.com>
Cc: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Subject: Re: [PATCH bootstrap/libjava] split org_omg.lo into smaller bits
Date: Wed, 02 Apr 2008 17:24:00 -0000	[thread overview]
Message-ID: <47F3C10F.3030007@redhat.com> (raw)
In-Reply-To: <20080402150908.GQ6430@tw.il.thewrittenword.com>

Peter O'Gorman wrote:
> Hi,
> 
> We ran into a build issue with gcc-4.2.3 on hppa-hp-hpux11.23 - the
> build failed when it ran out of memory. It could be fixed by splitting 
> gnu/xml and org/omg into smaller pieces. For trunk gnu/xml had already
> been divided up -
> http://gcc.gnu.org/ml/java-patches/2007-q1/msg00311.html so we just
> did the same to org/omg.
> 
> We still see maximum memory usage going to almost 600MB when building
> org_omg_CORBA.lo, so at some point it may be necessary to subdivide
> more, but this fixed it for us.
> 
> Tested by building gcc-4.2.3 on hppa-hp-hpux11.23, and building trunk
> on i386-unknown-linux and running the libjava tests with no
> regressions.
> 
> Ok for trunk?

2008-04-02  Peter O'Gorman  <pogma@thewrittenword.com>

	PR bootstrap/35216
	* scripts/makemake.tcl: Replace org/omg build with build of all
	its subpackages.
	* sources.am: Regenerate.
	* Makefile.in: Regenerate.

OK, thanks.

Andrew.

      reply	other threads:[~2008-04-02 17:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 15:09 Peter O'Gorman
2008-04-02 17:24 ` Andrew Haley [this message]

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=47F3C10F.3030007@redhat.com \
    --to=aph@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=pogma@thewrittenword.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).