From: "J.A. Magallon" <jamagallon@able.es>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "J.A. Magallon" <jamagallon@able.es>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix inlining with gcc3
Date: Fri, 27 Jun 2003 16:22:20 +0200 [thread overview]
Message-ID: <20030627142220.GC3242@werewolf.able.es> (raw)
In-Reply-To: <1056711001.4348.20.camel@dhcp22.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Fri, Jun 27, 2003 at 12:50:02 +0200
On 06.27, Alan Cox wrote:
> On Gwe, 2003-06-27 at 00:08, J.A. Magallon wrote:
> > This fixes inlining (really, not-inlining) with gcc3. How about next -pre ?
>
> Benchmark that before you blindly assume its right. Gcc not inlining large
> stuff actually appears to be _smarter_ than the authors of the code
>
Let's be clear, I just collect patches that I think are interesting. The
original post by Andrew Morton <akpm@digeo.com> is here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=104695003008386&w=2
Quoting it:
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
And I also remember other posts, by other author of a similar patch, that
claimed some critical functions not being inlined due to size (memcpys..).
Will try to look original info about that...
...here it is:
http://marc.theaimsgroup.com/?l=linux-kernel&m=103632312702693&w=2
--
J.A. Magallon <jamagallon@able.es> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.2 (Cooker) for i586
Linux 2.4.21-jam1 (gcc 3.3 (Mandrake Linux 9.2 3.3-2mdk))
next prev parent reply other threads:[~2003-06-27 14:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 22:03 Linux 2.4.22-pre2 Marcelo Tosatti
2003-06-26 22:54 ` J.A. Magallon
2003-06-26 23:06 ` [PATCH] gcc_check for x86 J.A. Magallon
2003-06-26 23:08 ` [PATCH] fix inlining with gcc3 J.A. Magallon
2003-06-26 23:36 ` Kurt Wall
2003-06-27 10:50 ` Alan Cox
2003-06-27 14:22 ` J.A. Magallon [this message]
2003-06-26 23:31 ` [PATCH] kill extra printk prototype J.A. Magallon
2003-06-27 14:02 ` Adrian Bunk
2003-06-26 23:32 ` [PATCH] kill duplicate pci_id J.A. Magallon
2003-06-27 5:59 ` Linux 2.4.22-pre2 Marc-Christian Petersen
2003-06-27 8:44 ` Matthias Andree
2003-06-27 17:58 ` [2.4 patch] some gcc 3.3 fixes from -ac Adrian Bunk
2003-06-27 18:56 ` Linux 2.4.22-pre2 Alessandro Suardi
2003-06-27 23:36 ` [BUG?] do_generic_direct_write J.A. Magallon
2003-07-04 20:55 ` J.A. Magallon
2003-06-27 23:38 ` Linux 2.4.22-pre2 Krzysztof Halasa
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=20030627142220.GC3242@werewolf.able.es \
--to=jamagallon@able.es \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.