From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id EF067B6EE7 for ; Thu, 19 Apr 2012 08:18:03 +1000 (EST) Message-ID: <1334787477.3143.18.camel@pasglop> Subject: Re: [PATCH 1/4] powerpc: Require gcc 4.0 on 64-bit From: Benjamin Herrenschmidt To: Kumar Gala Date: Thu, 19 Apr 2012 08:17:57 +1000 In-Reply-To: <85510A09-D78C-432E-AAED-A0FB49D5325A@kernel.crashing.org> References: <20120418144254.3286ce94@kryten> <85510A09-D78C-432E-AAED-A0FB49D5325A@kernel.crashing.org> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Cc: linuxppc-dev@lists.ozlabs.org, paulus@samba.org, Anton Blanchard List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 2012-04-18 at 09:28 -0500, Kumar Gala wrote: > On Apr 17, 2012, at 11:42 PM, Anton Blanchard wrote: > > > > > Older versions of gcc had issues with using -maltivec together with > > -mcpu of a non altivec capable CPU. We work around it by specifying > > -mcpu=970, but the logic is complicated. > > > > In preparation for adding more -mcpu targets, remove the workaround > > and just require gcc 4.0 for 64-bit builds. > > > > Signed-off-by: Anton Blanchard > > --- > > > > 4.0 came out in 2005 and the gcc on RHEL5 and SLES10 looks to be 4.1. > > I highly doubt a ppc64 kernel will build these days on either RHEL4 or > > SLES9. > > > > Anything else we have to worry about? > > There are probably embedded customers that might utilize older compilers, so this concerns me a little. For 64-bit ? I doubt it ... Cheers, Ben.