From: Willy Tarreau <willy@w.ods.org>
To: David Zaffiro <davzaffiro@netscape.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compiling x86 with and without frame pointer
Date: Thu, 21 Nov 2002 20:20:45 +0100 [thread overview]
Message-ID: <20021121192045.GE3636@alpha.home.local> (raw)
In-Reply-To: <3DDCA7C9.9040501@netscape.net>
On Thu, Nov 21, 2002 at 10:30:49AM +0100, David Zaffiro wrote:
> I use -momit-leaf-frame-pointer for optimization in some own projects,
> instead of the "-fomit-frame-pointer". For me, this results in better
> codesize/speed compared to both "-fomit-frame-pointer" or no option at
> all. Actually gcc-2.95 seems to support this feature as well, but it
> never made it into the 2.95 docs... It makes debugging a lot easier too.
>
> So anyone "caring to benchmark", could you please test the
> "-momit-leaf-frame-pointer" option for x86 as well...
Well, I tried on a 2.4.18+patches with gcc 2.95.3. bzImage is :
538481 bytes with -fomit-frame-pointer
538510 bytes with no particular flag
542137 bytes with -momit-leaf-frame-pointer.
So -fomit-frame-pointer shows the same as other's observation, but in this
particular case, -momit-leaf-frame-pointer made a slightly bigger kernel.
Didn't have time to inspect all sections, though.
Cheers,
Willy
next prev parent reply other threads:[~2002-11-21 19:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 4:47 Keith Owens
2002-11-21 5:06 ` Mark Mielke
2002-11-21 9:30 ` David Zaffiro
2002-11-21 19:20 ` Willy Tarreau [this message]
2002-11-21 19:32 ` Doug Ledford
2002-11-21 19:41 ` Willy Tarreau
2002-11-21 20:00 ` Doug Ledford
2002-11-25 8:47 ` David Zaffiro
2002-11-25 8:52 ` Willy Tarreau
2002-11-25 14:55 ` Denis Vlasenko
2002-11-25 15:00 ` Denis Vlasenko
2002-11-25 11:57 ` David Zaffiro
2002-11-21 12:55 ` Dave Jones
2002-11-21 14:46 ` Alan Cox
2002-11-21 17:44 ` Martin J. Bligh
2002-11-21 23:47 ` Rudmer van Dijk
2002-11-25 8:59 ` David Zaffiro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021121192045.GE3636@alpha.home.local \
--to=willy@w.ods.org \
--cc=davzaffiro@netscape.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®