public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matan Peled <chaosite@gmail.com>
To: linux-kernel@vger.kernel.org, Matan Peled <chaosite@gmail.com>
Cc: kwallinator@gmail.com
Subject: Re: Arjan's noinline Patch
Date: Mon, 02 Jan 2006 18:24:31 +0200	[thread overview]
Message-ID: <43B953BF.50602@gmail.com> (raw)
In-Reply-To: <20060102151429.GH5213@kurtwerks.com>

Kurt Wall wrote:
> 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

Yes, thats more like the rest of the results I seen... BTW, what is the .config?

Here are my results. Kernel is 2.6.15-rc7, gcc is 4.0.2 (Gentoo 4.0.2-r2, 
HTB-4.0.2-1.00, pie-8.7.8)

'ay' denotes allyesconfig, def is defconfig.

I believe that neither of these have OPTIMIZE_FOR_SIZE turned on, but I didn't 
play with that.

allyesconfig made a huge kernel, so I manually 'fixed' the formatting.

kaitou inlinetest # size *def*
    text	   data	    bss	    dec	    hex	filename
3676326	1084576	 584920	5345822	 51921e	vmlinux.def.inline
3658652	1085168	 584920	5328740	 514f64	vmlinux.def.noinline


kaitou inlinetest # size *ay*
     text	   data	    bss	     dec	    hex	filename
22911557	7523774	1997000	32432331	1eee0cb	vmlinux.ay.inline
22783415	7525934	1997000	32306349	1ecf4ad	vmlinux.ay.noinline


defconfig:
	17674 byte difference (0.4%) in text.

allyesconfig:
	128142 byte difference (0.6%) in text.

Unless my math is off, that is.

-- 
[Name      ]   ::  [Matan I. Peled    ]
[Location  ]   ::  [Israel            ]
[Public Key]   ::  [0xD6F42CA5        ]
[Keyserver ]   ::  [keyserver.kjsl.com]
encrypted/signed  plain text  preferred


  reply	other threads:[~2006-01-02 16:24 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
2006-01-02 16:24       ` Matan Peled [this message]
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=43B953BF.50602@gmail.com \
    --to=chaosite@gmail.com \
    --cc=kwallinator@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