From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <17017.42136.824607.253146@cargo.ozlabs.ibm.com> Date: Thu, 5 May 2005 14:44:08 +1000 From: Paul Mackerras To: Tom Rini In-Reply-To: <20050505041225.GX1221@smtp.west.cox.net> References: <17016.29775.224816.691409@cargo.ozlabs.ibm.com> <466e699745cf24e660e296530f6e34dc@embeddededge.com> <17017.16478.767293.191940@cargo.ozlabs.ibm.com> <45e21c1ae2899849665fb894a2adcc20@embeddededge.com> <17017.39523.745634.193331@cargo.ozlabs.ibm.com> <20050505041225.GX1221@smtp.west.cox.net> Cc: linuxppc-dev@ozlabs.org Subject: Re: [PATCH] Set cpu explicitly in kernel compiles List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Tom Rini writes: > So here's where the confusion comes in. You're saying that even though > (except .S files) no ppc32 kernel config was passing in explicit > -mcpu=... or similar, only CONFIG_6xx is hurt by the gcc4 biarch thingy? Indeed, we were never using -mcpu, and maybe we should be. The problem only comes up if you configure gcc4 as biarch. I can't imagine anyone building a biarch compiler for 4xx or 8xx. :) Alan Modra tells me that gcc4 can support all the ppc families in the one binary, and that you can specify what cpu to use as the assumed default at configure time. If you specify --with-cpu=xxx at configure time you get scheduling for that particular cpu. So yes, only CONFIG_6xx is affected by biarch gcc4 assuming POWER4. Other families would only be affected if you were using a generic gcc4, which won't work at present anyway, since we don't add -mcpu=xxx. Paul.