From: David Zaffiro <DavZaffiro@tasking.nl>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: Compiling x86 with and without frame pointer
Date: Mon, 25 Nov 2002 09:59:17 +0100 [thread overview]
Message-ID: <3DE1E665.1060907@netscape.net._> (raw)
In-Reply-To: 224900000.1037900678@flay
> I looked at 2.5.47 (with a splattering of performance patches) using
> gcc 2.95.4 (Debian Woody), on a 16-way NUMA-Q, and did some kernel
> compile testing. The times to do the tests were almost identical
> (within error noise), but the kernel was indeed smaller
>
> text data bss dec hex filename
> 1873293 396231 459388 2728912 29a3d0 2.5.47-mjb1/vmlinux
> 1427355 396875 455356 2279586 22c8a2 2.5.47-mjb1-frameptr/vmlinux
>
I can't think of any reason why the data- and bss-part of the kernel are
influenced by a framepointer option, this seems highly illogical. It
shouldn't make any difference as far as I can tell, maybe you altered
other options as well? (Could be strange compilerbehaviour though)
Keith's results seem more reliable:
# size 2.4.20-rc2-*/vmlinux
text data bss dec hex filename
2669584 337972 402697 3410253 34094d 2.4.20-rc2-fp/vmlinux
2676919 337972 402697 3417588 3425f4 2.4.20-rc2-nofp/vmlinux
prev parent reply other threads:[~2002-11-25 8:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 4:47 Compiling x86 with and without frame pointer Keith Owens
2002-11-21 5:06 ` Mark Mielke
2002-11-21 9:30 ` David Zaffiro
2002-11-21 19:20 ` Willy Tarreau
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 [this message]
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=3DE1E665.1060907@netscape.net._ \
--to=davzaffiro@tasking.nl \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.