From: Kurt Wall <kwall@kurtwerks.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Arjan's noinline Patch
Date: Sun, 1 Jan 2006 22:43:50 -0500 [thread overview]
Message-ID: <20060102034350.GD5213@kurtwerks.com> (raw)
In-Reply-To: <20060101155710.GA5213@kurtwerks.com>
On Sun, Jan 01, 2006 at 10:57:10AM -0500, Kurt Wall took 0 lines to write:
> After applying Arjan's noline patch (http://www.fenrus.org/noinlin), I
> see almost a 10% reduction in the size of .text (against 2.6.15-rc6)
> with no apparent errors and no reduction in functionality:
>
> $ size vmlinux.*
> text data bss dec hex filename
> 2578246 462000 479920 3520166 35b6a6 vmlinux.inline
> 2327319 462000 479920 3269239 31e277 vmlinux.noinline
The above was built with gcc 3.4.4. With gcc 4.0.2 on the same config:
$ size vmlinux.402.*
text data bss dec hex filename
2626474 461856 479984 3568314 3672ba vmlinux.402.inline
2313578 461800 479984 3255362 31ac42 vmlinux.402.noinline
An 11.9% size reduction in .text. What I also notice is the 4.0.2
appears to inline more aggressively than 3.4.4 because the same
config is almost 50K larger in the inline case when compiled with gcc
3.4.4. the "noinline" cases were built with Arjan's patch and
CONFIG_CC_OPTIMIZE_FOR_SIZE; the "inline" kernels were built,
obviously, without the patch and without CONFIG_CC_OPTIMIZE_FOR_SIZE.
Kurt
--
Fifth Law of Procrastination:
Procrastination avoids boredom; one never has the feeling that
there is nothing important to do.
next prev parent reply other threads:[~2006-01-02 3:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-01 15:57 Arjan's noinline Patch Kurt Wall
2006-01-01 16:12 ` Arjan van de Ven
2006-01-02 0:54 ` Kurt Wall
2006-01-02 3:43 ` Kurt Wall [this message]
2006-01-02 10:03 ` Matan Peled
2006-01-02 15:14 ` Kurt Wall
2006-01-02 16:24 ` Matan Peled
2006-01-02 16:30 ` Matan Peled
2006-01-03 1:20 ` Kurt Wall
2006-01-02 16:26 ` Kurt Wall
2006-01-02 18:51 ` Jan Engelhardt
2006-01-02 20:27 ` Matan Peled
2006-01-03 19:49 ` Jan Engelhardt
2006-01-02 22:06 ` Adrian Bunk
2006-01-02 11:04 ` Ingo Molnar
2006-01-02 15:21 ` Kurt Wall
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=20060102034350.GD5213@kurtwerks.com \
--to=kwall@kurtwerks.com \
--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