From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20153 invoked by alias); 7 Jul 2005 14:38:17 -0000 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 Received: (qmail 20138 invoked by uid 48); 7 Jul 2005 14:38:17 -0000 Date: Thu, 07 Jul 2005 14:38:00 -0000 Message-ID: <20050707143817.20136.qmail@sourceware.org> From: "klaus dot kusche at inode dot at" To: java-prs@gcc.gnu.org In-Reply-To: <20050707094458.22341.klaus.kusche@inode.at> References: <20050707094458.22341.klaus.kusche@inode.at> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libgcj/22341] Interix: gcj out of virtual mem during libgcj make X-Bugzilla-Reason: CC X-SW-Source: 2005-q3/txt/msg00033.txt.bz2 List-Id: ------- Additional Comments From klaus dot kusche at inode dot at 2005-07-07 14:38 ------- But on supported configurations (and afaik interix is one of them), an out-of- the-box gcc build (incl. libgcj) should not be guranteed to fail. This is no physical limit (memory size, swap space, ...), we tried on several different systems, all failed in the same way. It is a fundamental architectural problem: There is a 2 GB virtual address space limit for each process in Windows, and in combination with the way windows loads DLLs etc., gcc will hit this limit when building libgcj with the default settings, no matter how large the hardware is. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22341