|
From: Andrew H. <ap...@re...> - 2004-08-25 10:17:36
|
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. Only by 0.4%, which is nearly at the level of noise. Is this true of the other executables as well? Andrew. |