Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751206AbVL3Hth (ORCPT ); Fri, 30 Dec 2005 02:49:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751208AbVL3Hth (ORCPT ); Fri, 30 Dec 2005 02:49:37 -0500 Received: from mx2.mail.elte.hu ([157.181.151.9]:8603 "EHLO mx2.mail.elte.hu") by vger.kernel.org with ESMTP id S1751206AbVL3Hth (ORCPT ); Fri, 30 Dec 2005 02:49:37 -0500 Date: Fri, 30 Dec 2005 08:49:16 +0100 From: Ingo Molnar To: Tim Schmielau Cc: Arjan van de Ven , Linus Torvalds , Dave Jones , Andrew Morton , lkml , mpm@selenic.com Subject: Re: [patch 00/2] improve .text size on gcc 4.0 and newer compilers Message-ID: <20051230074916.GC25637@elte.hu> References: <20051228214845.GA7859@elte.hu> <20051228201150.b6cfca14.akpm@osdl.org> <20051229073259.GA20177@elte.hu> <20051229202852.GE12056@redhat.com> <20051229224839.GA12247@elte.hu> <1135897092.2935.81.camel@laptopd505.fenrus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-ELTE-SpamScore: -1.9 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.9 required=5.9 tests=ALL_TRUSTED,AWL autolearn=no SpamAssassin version=3.0.3 -2.8 ALL_TRUSTED Did not pass through any untrusted hosts 0.9 AWL AWL: From: address is in the auto white-list X-ELTE-VirusStatus: clean Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 594 Lines: 16 * Tim Schmielau wrote: > What about the previous suggestion to remove inline from *all* static > inline functions in .c files? i think this is a way too static approach. Why go from one extreme to the other, when my 3 simple patches (which arguably create a more flexible scenario) gives us savings of 7.7%? Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/