Date: Mon, 05 Aug 2002 14:39:29 -0700 From: Darren Pilgrim <dmp@pantherdragon.org> To: Jason Andresen <jandrese@mitre.org> Cc: Terry Lambert <tlambert2@mindspring.com>, Dmitry Morozovsky <marck@rinet.ru>, hackers@freebsd.org Subject: Re: -fomit-frame-pointer for the world build Message-ID: <3D4EF091.EA1C91D3@pantherdragon.org> References: <20020802212841.R58905-100000@woozle.rinet.ru> <3D4AC526.4CD399B3@mindspring.com> <3D4C8464.A2F4775A@pantherdragon.org> <3D4CC81F.94526C8A@mindspring.com> <3D4EA466.C1289F0F@mitre.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Jason Andresen wrote: > Terry Lambert wrote: > > The claimed savings are fictions. They are function call > > overhead savings assuming an average number of arguments and > > related pushed values, and they apply only to the call process > > itself. Most time in programs is spent in running, not calling > > functions, so if you expect an elimination of "18% overhead" > > to make you programs that much faster, you are dreaming. > > On the other hand, -fomit-frame-pointer is the only optimization > beyond -O in gcc that actually seems to offer any sort of speedup > for me. I've seen 10 to 20% reduction in runtime on some programs > with -fomit-frame-pointer. It's the only specific optimization I > bother with anymore. What, if anything, have you come across that won't compile/run properly when you use -fomit-frame-pointer? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D4EF091.EA1C91D3>