From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28480 invoked by alias); 5 Nov 2006 19:16:08 -0000 Received: (qmail 28459 invoked by uid 48); 5 Nov 2006 19:16:07 -0000 Date: Sun, 05 Nov 2006 19:16:00 -0000 Message-ID: <20061105191607.28458.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: java-prs@gcc.gnu.org From: "dberlin at gcc dot gnu dot org" Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org X-SW-Source: 2006-q4/txt/msg00096.txt.bz2 List-Id: ------- Comment #6 from dberlin at gcc dot gnu dot org 2006-11-05 19:16 ------- (In reply to comment #5) > Subject: Re: jc1: out of memory allocating 4072 bytes after a total of > 708630224 bytes > > > Except that all of these were fixed in the followup patch and a later > > typo fix, *including* the memory usage (see honza's tester). > > I may have been wrong above as to which java compilation caused the build > failure because make -j 4 was used. In any case, the compilation fails > with the gnu-xml.list. The backtrace is shown below. Seems to indicate > a problem with alias analysis My guess is that there must be a truly huge number of variables here and the sets must not be collapsing. Can you bzip2 compress -fdump-tree-alias-vops-details-blocks-stats (it's going to be very large) and put it somewhere for me? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29587