public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Egger <degger@fhm.edu>
To: Andrew Morton <akpm@digeo.com>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [patch] work around gcc-3.x inlining bugs
Date: 06 Mar 2003 21:32:12 +0100	[thread overview]
Message-ID: <1046982732.18897.34.camel@sonja> (raw)
In-Reply-To: <20030306032208.03f1b5e2.akpm@digeo.com>

[-- Attachment #1: Type: text/plain, Size: 845 bytes --]

Am Don, 2003-03-06 um 12.22 schrieb Andrew Morton:

> shrinks my 3.2.1-compiled kernel text by about 64 kbytes:
> 
>    text    data     bss     dec     hex filename
> 3316138  574844  726816 4617798  467646 vmlinux-before
> 3249255  555436  727204 4531895  4526b7 vmlinux-after
> 
> mnm:/tmp> nm vmlinux-before|grep __constant_c_and_count_memset | wc
>     233     699    9553
> mnm:/tmp> nm vmlinux-after|grep __constant_c_and_count_memset | wc
>      13      39     533

> Can anyone see a problem with it?

Looks good to me...

   text    data     bss     dec     hex filename
1842635  167450  140292 2150377  20cfe9 vmlinux
1867787  167450  140292 2175529  213229 vmlinux.old

I hope this doesn't trigger any latent compiler bugs but in this
case we should beat the gcc people to it...

-- 
Servus,
       Daniel

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-03-06 20:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-06 11:22 [patch] work around gcc-3.x inlining bugs Andrew Morton
2003-03-06 15:57 ` Jeff Garzik
2003-03-06 20:32 ` Daniel Egger [this message]
     [not found] <20030306032208.03f1b5e2.akpm@digeo.com.suse.lists.linux.kernel>
2003-03-06 11:52 ` Andi Kleen
2003-03-06 20:26   ` H. Peter Anvin
2003-03-06 21:28   ` Kurt Garloff
2003-03-09 22:40     ` Kurt Garloff

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=1046982732.18897.34.camel@sonja \
    --to=degger@fhm.edu \
    --cc=akpm@digeo.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