public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Kumar Gala <kumar.gala@freescale.com>
To: Steve Munroe <sjmunroe@us.ibm.com>
Cc: <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: Fri, 23 Sep 2005 15:29:00 -0000	[thread overview]
Message-ID: <1F5CED38-D49B-421B-A530-6892148EEF5C@freescale.com> (raw)
In-Reply-To: <OF11BDA2D0.E99C10BD-ON86257084.0077BF90-86257084.007AFAC3@us.ibm.com>

Steve,

Let's make sure not to over look the embedded and 32-bit processors.   
There are a number of variants here that include some user ISA  
extensions that you did not mention:

4xx MAC
Book-E isel
e500 embedded fp
e500 SPE

Are ones that come of the top of my head.  Additionally, I would say  
that Freescale has at least six different powerpc micro-architectures  
that it ships today:
     8xx, 603, 7400, 745x, e500, e200, (e700 in design)

Also, we have optimized some libc functions for 745x that take  
advantage of altivec and e500 that take advantage of SPE.

Anyways my point is lets make sure that any discussion includes ALL  
of powerpc, not just the ones shipping from IBM :)

- kumar

  parent reply	other threads:[~2005-09-23  5:20 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
2005-09-22 23:00   ` Paul Brook
2005-09-23 15:29 ` Kumar Gala [this message]
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=1F5CED38-D49B-421B-A530-6892148EEF5C@freescale.com \
    --to=kumar.gala@freescale.com \
    --cc=autoconf@gnu.org \
    --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).