Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932166AbWHVLSf (ORCPT ); Tue, 22 Aug 2006 07:18:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932171AbWHVLSf (ORCPT ); Tue, 22 Aug 2006 07:18:35 -0400 Received: from emailhub.stusta.mhn.de ([141.84.69.5]:42759 "HELO mailout.stusta.mhn.de") by vger.kernel.org with SMTP id S932166AbWHVLSf (ORCPT ); Tue, 22 Aug 2006 07:18:35 -0400 Date: Tue, 22 Aug 2006 13:18:35 +0200 From: Adrian Bunk To: Andi Kleen Cc: Kyle Moffett , linux-kernel@vger.kernel.org, Roman Zippel Subject: Re: [2.6 patch] re-add -ffreestanding Message-ID: <20060822111835.GU11651@stusta.de> References: <20060821212154.GO11651@stusta.de> <20060821232444.9a347714.ak@suse.de> <20060821214636.GP11651@stusta.de> <20060822000903.441acb64.ak@suse.de> <20060821222412.GS11651@stusta.de> <20060822002728.c023bf85.ak@suse.de> <20060821225837.GT11651@stusta.de> <20060822011320.a3491337.ak@suse.de> <20060822123713.78a5bcaf.ak@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060822123713.78a5bcaf.ak@suse.de> User-Agent: Mutt/1.5.12-2006-07-14 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1524 Lines: 42 On Tue, Aug 22, 2006 at 12:37:13PM +0200, Andi Kleen wrote: > On Mon, 21 Aug 2006 23:37:31 -0400 > Kyle Moffett wrote: > > > On Aug 21, 2006, at 19:13:20, Andi Kleen wrote: > > >> What's the problem with adding -ffreestanding and stating > > >> explicitely which functions we want to be handled be builtins, and > > >> which functions we don't want to be handled by builtins? > > > > > > Take a look at lib/string.c and think about it a bit. > > > > So why can't lib/string.c explicitly say __builtin_foo() instead of > > foo() where we mean the former? > > Because gcc when using builtins sometimes decides to call the > out of line version (usually when it can't figure out the alignment > and generic alignment code would be too large to inline). And it will > always call str/memfoo not __builtin_str/memfoo IOW, we might in some cases require an out-of-line version of the function? I don't see in this case any problem created by using -ffreestanding and the #define's. > -Andi cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed - 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/