------- 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 don't have any shell limits (as > reported per "ulimit -a") that would match this number, do you? >
I don't think so. We run large memory jobs on that machine (that's why we have it in the first place). I get the following output: > ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited pending signals (-i) 529920 max locked memory (kbytes, -l) 32 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 529920 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32439
