This is the mail archive of the java-patches@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]

Re: Patch: FYI: split up parser build

From: Gerald Pfeifer <gerald at pfeifer dot com>
To: Tom Tromey <tromey at redhat dot com>
Cc: GCJ-patches <java-patches at gcc dot gnu dot org>
Date: Tue, 6 Feb 2007 21:26:08 +0100 (CET)
Subject: Re: Patch: FYI: split up parser build
References: <m3bqkfrp1b.fsf@localhost.localdomain> <Pine.LNX.4.64.0702021605330.10525@acrux.dbai.tuwien.ac.at> <m3hcu4cty7.fsf@localhost.localdomain>

On Fri, 2 Feb 2007, Tom Tromey wrote:
> Feel like trying it with exp.complexity removed?  :)  That would be
> above and beyond.

This doesn't save us sufficient amounts of memory, I'm afraid.  I now
worked around the increased memory consumption by means of the system
configuration trick I posted over the weekend, and if there are no
further complaints about this it's probably not of too high a priority
(though we may not have hit users yet, and developers usually have nice
machines ;-).

Do you see any other idea to reduce memory consumption that leads to
the failure building gnu/javax/swing/text/html/parser/HTML_401F.lo?

Gerald

Follow-Ups:
- Re: Patch: FYI: split up parser build
  - From: Tom Tromey

References:
- Patch: FYI: split up parser build
  - From: Tom Tromey
- Re: Patch: FYI: split up parser build
  - From: Gerald Pfeifer
- Re: Patch: FYI: split up parser build
  - From: Tom Tromey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]