From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22135 invoked by alias); 22 Sep 2005 22:44:40 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 22055 invoked by uid 22791); 22 Sep 2005 22:44:29 -0000 Received: from dumbledore.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.11) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 22 Sep 2005 22:44:29 +0000 Received: (qmail 5264 invoked from network); 22 Sep 2005 22:44:27 -0000 Received: from unknown (HELO 81-178-138-140.dsl.pipex.com) (paul@127.0.0.2) by mail.codesourcery.com with ESMTPA; 22 Sep 2005 22:44:27 -0000 From: Paul Brook To: binutils@sources.redhat.com Subject: Re: [RFC] Additional targets for powerpc Date: Thu, 22 Sep 2005 22:58:00 -0000 User-Agent: KMail/1.8.2 Cc: Steve Munroe , libc-alpha@sources.redhat.com, gcc@gcc.gnu.com, binutils@sourceware.org, autoconf@gnu.org, Roland McGrath References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200509222344.25797.paul@codesourcery.com> X-SW-Source: 2005-09/txt/msg00260.txt.bz2 On Thursday 22 September 2005 23:23, Steve Munroe wrote: > Introduction > > It has become increasingly clear that PowerPC processor family needs > additional (machine) targets for the Linux distributions. At present, > Linux only has two targets (powerpc32 and powerpc64, powerpc is synonym > for powerpc32) for PowerPC. These targets only address the two operating > modes (32- and 64-bit) and don't address the wide range of processor > families and chips available. With only one target per mode, we are forced > to compile for a common subset of powerpc instructions and default > instruction scheduling. Isn't the --with-cpu= gcc configure option sufficient? This seems to work for Arm targets, which probably have as much variation as PPC. gcc is configured with --with-cpu=whatever or --with-arch=whatever, and everything else else figures it out from what the compiler. Paul From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22355 invoked by alias); 22 Sep 2005 22:44:41 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 22056 invoked by uid 22791); 22 Sep 2005 22:44:29 -0000 Received: from dumbledore.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.11) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 22 Sep 2005 22:44:29 +0000 Received: (qmail 5264 invoked from network); 22 Sep 2005 22:44:27 -0000 Received: from unknown (HELO 81-178-138-140.dsl.pipex.com) (paul@127.0.0.2) by mail.codesourcery.com with ESMTPA; 22 Sep 2005 22:44:27 -0000 From: Paul Brook To: binutils@sources.redhat.com Subject: Re: [RFC] Additional targets for powerpc Date: Thu, 22 Sep 2005 23:00:00 -0000 User-Agent: KMail/1.8.2 Cc: Steve Munroe , libc-alpha@sources.redhat.com, gcc@gcc.gnu.com, binutils@sourceware.org, autoconf@gnu.org, Roland McGrath References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-ID: <200509222344.25797.paul@codesourcery.com> X-SW-Source: 2005-09/txt/msg00261.txt.bz2 Message-ID: <20050922230000.D_9ibKhM_e9eX_xf9yNKP7APH8o6nj_n8GbElmmA5mQ@z> On Thursday 22 September 2005 23:23, Steve Munroe wrote: > Introduction > > It has become increasingly clear that PowerPC processor family needs > additional (machine) targets for the Linux distributions. At present, > Linux only has two targets (powerpc32 and powerpc64, powerpc is synonym > for powerpc32) for PowerPC. These targets only address the two operating > modes (32- and 64-bit) and don't address the wide range of processor > families and chips available. With only one target per mode, we are forced > to compile for a common subset of powerpc instructions and default > instruction scheduling. Isn't the --with-cpu= gcc configure option sufficient? This seems to work for Arm targets, which probably have as much variation as PPC. gcc is configured with --with-cpu=whatever or --with-arch=whatever, and everything else else figures it out from what the compiler. Paul