From: Ryan Arnold <ryan.arnold@gmail.com>
To: libc-ports <libc-ports@sourceware.org>
Cc: luisgpm@linux.vnet.ibm.com, Todd Iglehart <iglehart@us.ibm.com>,
Josh Boyer <jwboyer@linux.vnet.ibm.com>,
rsa@us.ibm.com
Subject: Re: [PATCH] powerpc: 405/440/464/476 support and optimizations
Date: Tue, 18 Jan 2011 13:16:00 -0000 [thread overview]
Message-ID: <AANLkTi=exjK4EvGG9FoU+iK8W3XjYzWew8q3o_t20URu@mail.gmail.com> (raw)
In-Reply-To: <1292271927.3622.6.camel@localhost.localdomain>
On Mon, Dec 13, 2010 at 2:25 PM, Ryan Arnold <rsa@us.ibm.com> wrote:
> Sorry for the delinquent response. This looks good to me and I think it
> should be checked in.
>
> I'd like for someone with a 405, 440, or 464 to test it further. As far
> as we know the code only uses instructions available on all of these
> platforms.
>
> I'd like to stress that it was authored by Todd Iglehart
> <iglehart@us.ibm.com> and contributed by IBM. Luis did the fixup and
> authored the implies structure.
>
> Ryan S. Arnold
I've checked this patch into glibc-ports under:
commit # a72cc2b29d00207fd8e2ee4612502339a14816b6
Just a general note on configuration; some of these processors have a
floating point unit but I believe all of them default to soft-fp.
GLIBC configure won't recognize --with-cpu=476fp even though the
compiler might recognize -mcpu=476fp.
If you want to configure a hard-fp build just pass --with-cpu=476
--with-fp instead and a new Makefile fragment will make sure that
-mhard-float is added to CFLAGS and ASFLAGS.
Ryan S. Arnold
next prev parent reply other threads:[~2011-01-12 19:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 17:34 Luis Machado
2010-09-03 14:45 ` Ryan Arnold
2010-09-03 15:00 ` Luis Machado
2010-10-04 18:54 ` Luis Machado
2010-12-13 20:26 ` Ryan Arnold
2011-01-18 13:16 ` Ryan Arnold [this message]
2011-01-25 21:32 ` Joseph S. Myers
2012-01-18 20:31 ` acrux@cruxppc.org
2012-01-19 19:35 ` Carlos O'Donell
2012-01-20 14:24 ` acrux
2012-01-20 15:52 ` Ryan S. Arnold
2012-01-20 18:03 ` Carlos O'Donell
2012-01-23 0:41 ` acrux
2012-01-23 15:48 ` Ryan S. Arnold
2012-01-24 16:47 ` acrux
2012-01-24 17:20 ` Ryan S. Arnold
2012-01-24 17:41 ` acrux
2012-01-24 17:59 ` Ryan S. Arnold
2012-02-18 2:06 ` acrux
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='AANLkTi=exjK4EvGG9FoU+iK8W3XjYzWew8q3o_t20URu@mail.gmail.com' \
--to=ryan.arnold@gmail.com \
--cc=iglehart@us.ibm.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=libc-ports@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.com \
--cc=rsa@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).