Re: severe gcc problems
Re: severe gcc problems
- Subject: Re: severe gcc problems
- From: Greg Parker <email@hidden>
- Date: Mon, 18 Jul 2005 13:35:49 -0700
g++ -c -o d_iDS_d_EX_delta.o -g -O3 d_iDS_d_EX_delta.c
cc1plus(1322) malloc: *** vm_allocate(size=3888427008) failed
(error code=3)
This is failing because it is trying to allocate nearly 4GB of
memory. This will clearly fail in a 32 bit process like the
compiler. Whether this was caused by a compiler problem or
something in the code, there is not enough information to even guess.
I don't know, the source code is just 221K but there's a horde of
overloaded operators. 220,772 B vs 3.8G is almost 17,600 times
difference! I never thought that compiler might ever need so much
memory.
Try building without -g. gcc is rather space-inefficient with debug
information, especially in some C++ code. You might also try -gfull
instead of -g, which works better in some cases.
--
Greg Parker email@hidden Runtime Wrangler
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden