public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Serge Belyshev <33554432@mtu-net.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch/i386/Makefile,scripts/gcc-version.sh,Makefile small fixes
Date: Sat, 24 Jan 2004 10:17:04 -0800	[thread overview]
Message-ID: <20040124101704.3bf3ada2.akpm@osdl.org> (raw)
In-Reply-To: <87oestsard.fsf@mtu-net.ru>

Serge Belyshev <33554432@mtu-net.ru> wrote:
>
> [This patch is against 2.6.2-rc1-mm2]

Is appreciated, thanks.

> arch/i386/Makefile:
> *  omitted $(KBUILD_SRC)/ in script call.

OK

> scripts/gcc-version.sh:
> *  GNU tail no longer supports 'tail -1' syntax.

OK.

> Makefile: 
> *  There is no point in adding -funit-at-a-time option because it is
>    enabled by default at levels -Os, -O2 and -O3.

hm.  Didn't Andi say that adding -fno-unit-at-a-time caused code shrinkage?

> *  Consider adding -fweb option:

What does it do?

>    vanilla:
>    $ size vmlinux
>       text    data     bss     dec     hex filename
>    3056270  526780  386056 3969106  3c9052 vmlinux
> 
>    with -fweb:
>    $ size vmlinux
>       text    data     bss     dec     hex filename
>    3049523  526780  386056 3962359  3c75f7 vmlinux
> 
>    Also note 0.1 ... 1.0% speedup in various benchmarks.
>    This option is not enabled by default at -O2 because it
>    (like -fomit-frame-pointer) makes debugging impossible.

OK, then we'd need a config option for it.



  reply	other threads:[~2004-01-24 18:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-24 14:04 [PATCH] arch/i386/Makefile,scripts/gcc-version.sh,Makefile small fixes Serge Belyshev
2004-01-24 18:17 ` Andrew Morton [this message]
2004-01-24 18:32   ` Valdis.Kletnieks
2004-01-25  1:55     ` Serge Belyshev
2004-01-25  1:40   ` Serge Belyshev
  -- strict thread matches above, loose matches on Subject: below --
2004-01-24 14:37 sam

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=20040124101704.3bf3ada2.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=33554432@mtu-net.ru \
    --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