[Valgrind-developers] Memcheck optimisation level; Makefile.am includes

[Andrew Haley]

Nicholas Nethercote writes:
 > On Wed, 25 Aug 2004, Florian Weimer wrote:
 > 
 > >> 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.)
 > 
 > Ah, I didn't think of that, I think it answers the question... for 
 > vgskin_lackey.so, I get the following sizes:
 > 
 >    normal:               26577
 >    -fomit-fp:            27299
 > 
 >    normal stripped:       7780
 >    -fomit-fp stripped:    7748
 > 
 > The stripped versions look as expected, ie. with -fomit-fp it is smaller. 
 > It's interesting to see this effect, and good to know why it occurs.

Here you are:

/tmp/vgskin_lackey.so-normal
 27 .debug_frame  00000144  00000000  00000000  0000418c  2**2
                  CONTENTS, READONLY, DEBUGGING

/tmp/vgskin_lackey.so-fomitfp
 27 .debug_frame  000003f8  00000000  00000000  00004164  2**2
                  CONTENTS, READONLY, DEBUGGING