This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [Valgrind-developers] Memcheck optimisation level; Makefile.am includes
- From: Florian Weimer <fw at deneb dot enyo dot de>
- To: Nicholas Nethercote <njn25 at cam dot ac dot uk>
- Cc: Julian Seward <jseward at acm dot org>, Valgrind Developers <valgrind-developers at lists dot sourceforge dot net>, gcc at gcc dot gnu dot org
- Date: Wed, 25 Aug 2004 11:55:42 +0200
- Subject: Re: [Valgrind-developers] Memcheck optimisation level; Makefile.am includes
- References: <Pine.LNX.4.60.0408241209100.28550@hermes-1.csi.cam.ac.uk><1093388744.4449.15.camel@localhost><1093410677.3058.29.camel@camp4.serpentine.com><200408250920.24024.jseward@acm.org><Pine.LNX.4.60.0408251012491.8646@hermes-1.csi.cam.ac.uk>
* Nicholas Nethercote:
> So why are the total file sizes larger with -fomit-frame-pointer?
Have you already ruled out debugging information? Since you compile
with -g, this seems the most likely culprit. (If there is not frame
pointer, more debugging information is needed to access local
variables, so this growth isn't really avoidable.)