From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8103 invoked by alias); 31 Oct 2006 15:39:23 -0000 Received: (qmail 7758 invoked by alias); 31 Oct 2006 15:39:00 -0000 Date: Tue, 31 Oct 2006 15:39:00 -0000 Message-ID: <20061031153900.7757.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug java/29587] jc1: out of memory allocating 4072 bytes after a total of 708630224 bytes In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dave at hiauly1 dot hia dot nrc dot ca" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-10/txt/msg02705.txt.bz2 List-Id: ------- Comment #2 from dave at hiauly1 dot hia dot nrc dot ca 2006-10-31 15:38 ------- Subject: Re: jc1: out of memory allocating 4072 bytes after a total of 708630224 bytes > > jc1: out of memory allocating 4072 bytes after a total of 708630224 bytes > > > > similiar problem here. > > hppa2.0w-hp-hpux11.00 > gcc-4.2.0 revison 118176 I've been trying to pin down when this was introduced. This is somewhat tricky. Things seemed ok at revision 117843: . Then, for other reasons the build of libjava was broken for a couple of days. Then, the 4.2 branch was created. The problem appears to only be present in the 4.2 branch. Given that this is a apparently a garbage collection issue, it could be that this failure isn't related to any specified patch, but is caused by bad garbage collection limits. Dave -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29587