This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
mainline wants too much memory?
- From: Andrew Haley <aph at redhat dot com>
- To: Eyal Lebedinsky <eyal at eyal dot emu dot id dot au>
- Cc: gcc list <gcc at gcc dot gnu dot org>
- Date: Tue, 25 May 2004 11:04:17 +0100
- Subject: mainline wants too much memory?
- References: <40B3170B.8020908@eyal.emu.id.au>
Eyal Lebedinsky writes:
> Before I dig deeper, I wonder if this is reasonable. I am compiling a very large
> C program (mostly generated DB mode)
> -rw-rw-r-- 1 eyal ssa 38258830 May 25 13:00 sqlops.c
>
> and it runs out of memory with the below message. I find the ammount of
> requested memory (1,330,363,688 bytes) substantial.
>
> This is mainline off cvs today. Note
> -fmudflapth
> -O0 -fno-inline
>
> /usr/local/gcc-3.5/bin/i686-pc-linux-gnu-gcc-3.5.0 -I.
> -I/home/eyal/20040525g-mfi/h -W -Wall -Wshadow -Wpointer-arith -Wcast-qual
> -Wcast-align -Wconversion -Wredundant-decls -ansi -D_XOPEN_SOURCE=1
> -D_GNU_SOURCE=1 -fmudflapth -O0 -fno-inline -g
> -I/home/oracle/920/precomp/public -DSSA_ORA_PROC_VER=81 -O0 -c sqlops.c
>
> cc1: out of memory allocating 1330363688 bytes after a total of 133231372
> bytes
> make: *** [sqlops.o] Error 1
It's probably a bug. Run cc1 inside gdb and look at a backtrace of,
say, the last 10 stack frames.
Andrew.