This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [Valgrind-developers] Memcheck optimisation level; Makefile.amincludes
- From: Andrew Haley <aph at redhat dot com>
- To: Falk Hueffner <hueffner at informatik dot uni-tuebingen dot de>
- Cc: Nicholas Nethercote <njn25 at cam dot ac dot uk>, 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:05:24 +0100
- Subject: Re: [Valgrind-developers] Memcheck optimisation level; Makefile.amincludes
- 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><87u0uriliq.fsf@informatik.uni-tuebingen.de>
Falk Hueffner writes:
> Nicholas Nethercote <njn25@cam.ac.uk> writes:
>
> > So why are the total file sizes larger with -fomit-frame-pointer? Do
> > any GCC people know?
>
> One reason might be that accessing relative to stack pointer takes one
> byte more than relative to frame pointer:
Could be, but 7%? I really want to see those files.
Andrew.