From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sunset.davemloft.net (unknown [74.93.104.97]) by ozlabs.org (Postfix) with ESMTP id 474E4DDEF2 for ; Sat, 3 May 2008 07:40:11 +1000 (EST) Date: Fri, 02 May 2008 14:40:09 -0700 (PDT) Message-Id: <20080502.144009.147804001.davem@davemloft.net> To: galak@kernel.crashing.org Subject: Re: [PATCH] [POWERPC] Fix bootwrapper builds with newer gcc versions From: David Miller In-Reply-To: <3B083683-CB6E-4F1D-87EF-BBFA7D491271@kernel.crashing.org> References: <8CB3566C-F433-4457-906D-247BBB8D5505@kernel.crashing.org> <56cafb8cfeb954984d6e400c3de789b8@kernel.crashing.org> <3B083683-CB6E-4F1D-87EF-BBFA7D491271@kernel.crashing.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Kumar Gala Date: Fri, 2 May 2008 16:28:36 -0500 > Sorry, I meant the gcc patch. I'm not sure if this has been committed > to FSF head or not. If that's the case it would be a good idea to suggest a command line option to disable the new out-of-line code generation feature of that patch. But if the stubs it calls are really simple, you can just add implementations under arch/powerpc/lib/, and therefore it's not such a big deal. This is what we've traditionally done with libcalls generated by gcc for runtime support.