From: Paul Brook <paul@codesourcery.com>
To: binutils@sources.redhat.com
Cc: Steve Munroe <sjmunroe@us.ibm.com>,
libc-alpha@sources.redhat.com, gcc@gcc.gnu.com,
binutils@sourceware.org, autoconf@gnu.org,
Roland McGrath <roland@redhat.com>
Subject: Re: [RFC] Additional targets for powerpc
Date: Thu, 22 Sep 2005 22:58:00 -0000 [thread overview]
Message-ID: <200509222344.25797.paul@codesourcery.com> (raw)
In-Reply-To: <OF11BDA2D0.E99C10BD-ON86257084.0077BF90-86257084.007AFAC3@us.ibm.com>
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
WARNING: multiple messages have this Message-ID
From: Paul Brook <paul@codesourcery.com>
To: binutils@sources.redhat.com
Cc: Steve Munroe <sjmunroe@us.ibm.com>,
libc-alpha@sources.redhat.com, gcc@gcc.gnu.com,
binutils@sourceware.org, autoconf@gnu.org,
Roland McGrath <roland@redhat.com>
Subject: Re: [RFC] Additional targets for powerpc
Date: Thu, 22 Sep 2005 23:00:00 -0000 [thread overview]
Message-ID: <200509222344.25797.paul@codesourcery.com> (raw)
Message-ID: <20050922230000.D_9ibKhM_e9eX_xf9yNKP7APH8o6nj_n8GbElmmA5mQ@z> (raw)
In-Reply-To: <OF11BDA2D0.E99C10BD-ON86257084.0077BF90-86257084.007AFAC3@us.ibm.com>
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
next prev parent reply other threads:[~2005-09-22 22:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 22:44 Steve Munroe
2005-09-22 22:57 ` Ian Lance Taylor
2005-09-22 23:01 ` Roland McGrath
2005-09-22 23:01 ` Daniel Jacobowitz
2005-09-22 23:06 ` Ian Lance Taylor
2005-09-23 0:35 ` Doug Evans
2005-09-23 10:28 ` Roland McGrath
2005-09-22 23:02 ` Ian Lance Taylor
2005-09-23 5:20 ` Doug Evans
2005-09-22 22:58 ` Paul Brook [this message]
2005-09-22 23:00 ` Paul Brook
2005-09-23 15:29 ` Kumar Gala
2005-09-23 16:38 ` Steve Munroe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200509222344.25797.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=autoconf@gnu.org \
--cc=binutils@sources.redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.com \
--cc=libc-alpha@sources.redhat.com \
--cc=roland@redhat.com \
--cc=sjmunroe@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).