public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tomas Kalibera <kalibera@cs.purdue.edu>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Can GCC use more than 4G while compiling ?
Date: Fri, 15 Feb 2008 00:04:00 -0000	[thread overview]
Message-ID: <47B4D705.8090205@cs.purdue.edu> (raw)
In-Reply-To: <m3odakjda2.fsf@localhost.localdomain>

Ian Lance Taylor wrote:
> Tomas Kalibera <kalibera@cs.purdue.edu> 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.
>   

Thanks! This helped.

I assume that it might also help to override GGC_QUIRE_SIZE (now it's 
set in ggc-page.c to 256, when mmap is used). But I did not check.

Tomas

      reply	other threads:[~2008-02-15  0:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 23:07 Tomas Kalibera
2008-02-14  2:06 ` Ian Lance Taylor
2008-02-14  5:19   ` Tomas Kalibera
2008-02-14  5:52     ` Ian Lance Taylor
2008-02-15  0:04       ` Tomas Kalibera [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47B4D705.8090205@cs.purdue.edu \
    --to=kalibera@cs.purdue.edu \
    --cc=gcc-help@gcc.gnu.org \
    --cc=iant@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).