From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16348 invoked by alias); 14 Feb 2008 05:52:44 -0000 Received: (qmail 16340 invoked by uid 22791); 14 Feb 2008 05:52:44 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 14 Feb 2008 05:52:22 +0000 Received: from zps75.corp.google.com (zps75.corp.google.com [172.25.146.75]) by smtp-out.google.com with ESMTP id m1E5q5cq026918; Thu, 14 Feb 2008 05:52:06 GMT Received: from smtp.corp.google.com (spacemonkey1.corp.google.com [192.168.120.115]) by zps75.corp.google.com with ESMTP id m1E5q4UT017469 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 13 Feb 2008 21:52:05 -0800 Received: from localhost.localdomain.google.com (adsl-76-249-168-94.dsl.pltn13.sbcglobal.net [76.249.168.94]) (authenticated bits=0) by smtp.corp.google.com (8.13.8/8.13.8) with ESMTP id m1E5q3eq022157 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 13 Feb 2008 21:52:04 -0800 To: Tomas Kalibera Cc: gcc-help@gcc.gnu.org Subject: Re: Can GCC use more than 4G while compiling ? References: <47B37803.4020205@cs.purdue.edu> <47B3CF54.4060904@cs.purdue.edu> From: Ian Lance Taylor Date: Thu, 14 Feb 2008 05:52:00 -0000 In-Reply-To: <47B3CF54.4060904@cs.purdue.edu> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2008-02/txt/msg00144.txt.bz2 Tomas Kalibera writes: > > What is the exact error message? Are all the compiler binaries 64-bit > > executables? > > > - "virtual memory exhausted: Cannot allocate memory" OK, that means that a call to mmap using MAP_ANONYMOUS returned MAP_FAILED with errno set to ENOMEM. I see from the mmap man page that that can happen when the process's has reached the maximum number of mappings. It seems at least possible that you are running out of maps before you are running out of memory. On a GNU/Linux system you can see the maximum map count with "/sbin/sysctl vm.max_map_count". You can change that value using /sbin/sysctl -w. > I'm now trying my luck with > > "--param ggc-min-expand=0 --param ggc-min-heapsize=4096" > > Compilation is now by orders of magnitude slower, it's been already > compiling the single file for 6 hours, I don't know how far it got. Those options are just going to make the compiler run much slower, they are unlikely to reduce the maximum amount of allocated memory. > OK, and there is not any special option needed when compiling the gcc > compiler ? No. Ian