From: Kurt Wall <kwallinator@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Matan Peled <chaosite@gmail.com>
Subject: Re: Arjan's noinline Patch
Date: Mon, 2 Jan 2006 10:14:29 -0500 [thread overview]
Message-ID: <20060102151429.GH5213@kurtwerks.com> (raw)
In-Reply-To: <43B8FA70.2090408@gmail.com>
On Mon, Jan 02, 2006 at 12:03:28PM +0200, Matan Peled took 0 lines to write:
> Kurt Wall wrote:
> >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.
>
> Wait, so how do we know if its GCC's -Os that caused the reduction in .text
> size, or the noinline patch ... ?
Right, I need to isolate the effects of each variable. Results for gcc
3.4.4 and 4.0.2, built with CONFIG_CC_OPTIMIZE_FOR_SIZE enabled, appear
below. Pardon the bad methodology.
$ size vmlinux.*
text data bss dec hex filename
2333474 461848 479920 3275242 31f9ea vmlinux.344.inline
2327319 462000 479920 3269239 31e277 vmlinux.344.noinline
2319085 461608 479984 3260677 31c105 vmlinux.402.inline
2313578 461800 479984 3255362 31ac42 vmlinux.402.noinline
Kurt
--
Those who do not understand Unix are condemned to reinvent it, poorly.
-- Henry Spencer
next prev parent reply other threads:[~2006-01-02 15:11 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
2006-01-02 10:03 ` Matan Peled
2006-01-02 15:14 ` Kurt Wall [this message]
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=20060102151429.GH5213@kurtwerks.com \
--to=kwallinator@gmail.com \
--cc=chaosite@gmail.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