--- Comment #8 from jv244 at cam dot ac dot uk 2007-07-06 08:23 ---
closing as magically fixed
--
jv244 at cam dot ac dot uk changed:
What|Removed |Added
Stat
--- Comment #7 from jv244 at cam dot ac dot uk 2007-06-27 12:18 ---
(In reply to comment #6)
> (In reply to comment #3)
> > So, it looks like something inside gcc is hard-coded to just 1Gb
> > of memory, instead of the available memory.
>
> That's probably a stupid thing to ask, but you
--- Comment #6 from fxcoudert at gcc dot gnu dot org 2007-06-27 08:51
---
(In reply to comment #3)
> So, it looks like something inside gcc is hard-coded to just 1Gb
> of memory, instead of the available memory.
That's probably a stupid thing to ask, but you don't have any shell limits
--- Comment #5 from jv244 at cam dot ac dot uk 2007-06-27 07:31 ---
could be similar to PR32514
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32439
--- Comment #4 from pinskia at gmail dot com 2007-06-26 15:20 ---
Subject: Re: hard-coded memory limit ? f951: out of memory with '-O1
-fbounds-check'
On 26 Jun 2007 14:59:27 -, jv244 at cam dot ac dot uk
<[EMAIL PROTECTED]> wrote:
> f951: out of memory allocating 4064 bytes after
On 26 Jun 2007 14:59:27 -, jv244 at cam dot ac dot uk
<[EMAIL PROTECTED]> wrote:
f951: out of memory allocating 4064 bytes after a total of 1148219392 bytes
Ignore the second number, it just is total count of memory allocated
via xmalloc and not the amount of memory used at the time of the
--- Comment #3 from jv244 at cam dot ac dot uk 2007-06-26 14:59 ---
I ran the compilation now on a machine with 64Gb of memory, and it still
failed.
According to 'top' the memory used by f951 was about 4Gb. The error message:
f951: out of memory allocating 4064 bytes after a total of
