public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Linda Walsh <lkml@tlinx.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Save 320K on production machines?
Date: Mon, 27 Mar 2006 02:22:04 -0800	[thread overview]
Message-ID: <4427BCCC.4080506@tlinx.org> (raw)
In-Reply-To: <20060326100639.GE4053@stusta.de>

Adrian Bunk wrote:
> On Sun, Mar 26, 2006 at 11:24:15AM +0200, Jan Engelhardt wrote
>>> ** primarily "funit-at-a-time", though -fweb &
>>> -frename-registers may add a bit (GCC 3.3.5 as
>>> patched by SuSE; Maybe extra optimizations could
>>> be a "CONFIG" option much like regparms is now?
>>>       
>> IIRC, -funit-at-a-time with gcc3 made compiled code go bloat.
>>     
> That's wrong, the compiled code is smaller.
>   
>> Jan Engelhardt
>>     
> cu
> Adrian
>   
---
    That's my point -- if the code is optimized and it shrinks the code 
size
due to unnecessary path duplication, the remain code is more likely
to fit in the CPU cache (getting some performance benefits as well
faster in the process), isn't that a good reason to use it?

This was measured on a Pentium-III, SMP optioned kernel.  I'm sure it
will help my code fit just a little better in the runtime caches, no?

The current makefile turns on the optimization only on gcc4 or higher,
but my results were with gcc3.5.5.  Maybe defaults for 386 should
enabler the optimization for some versions of gcc 3 as well?  
-l


  reply	other threads:[~2006-03-27 10:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-26  8:31 Save 320K on production machines? Linda Walsh
2006-03-26  9:24 ` Jan Engelhardt
2006-03-26 10:06   ` Adrian Bunk
2006-03-27 10:22     ` Linda Walsh [this message]
2006-03-27 11:36       ` Paulo Marques
2006-03-30 21:34         ` Linda Walsh
2006-03-31  9:43           ` Adrian Bunk
2006-03-31  9:48           ` Jörn Engel
2006-03-26 10:39 ` Andre Tomt
2006-03-27 10:05   ` Linda Walsh
2006-03-28 14:29     ` Jan Engelhardt

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=4427BCCC.4080506@tlinx.org \
    --to=lkml@tlinx.org \
    --cc=bunk@stusta.de \
    --cc=jengelh@linux01.gwdg.de \
    --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