From: Hongli Lai Date: 2009-01-13T07:49:38+09:00 Subject: [ruby-core:21295] Re: [PATCH] Promising C coding techniques to reduce MRI's memory use Brent Roman wrote: > That's not the way the gcc behaves in my experience with the 32-bit x86 > machines. > Could you point me at this documentation? > > What I read is: > -O also turns on -fomit-frame-pointer on machines where doing so does > not interfere with debugging. > > 32-bit x86 machines cannot generate stack backtraces without framepointers. > This certainly does interfere with debugging. Both 'info gcc' and the online manual[1] say "-fomit-frame-pointer ... Enabled at levels -O, -O2, -O3, -Os." But if your experience is different then I guess it's a mistake in the documentation. [1] http://gcc.gnu.org/onlinedocs/gcc-4.3.2/gcc/Optimize-Options.html#index-fomit_002dframe_002dpointer-619 -- Phusion | The Computer Science Company Web: http://www.phusion.nl/ E-mail: info@phusion.nl Chamber of commerce no: 08173483 (The Netherlands)