From: Michael Ellerman <michael@ellerman.id.au>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: add vr save/restore functions
Date: Thu, 09 Jan 2014 11:09:55 +1100 [thread overview]
Message-ID: <1389226195.25505.3.camel@concordia> (raw)
In-Reply-To: <87fvoypznh.fsf@igel.home>
On Wed, 2014-01-08 at 10:54 +0100, Andreas Schwab wrote:
> Michael Ellerman <michael@ellerman.id.au> writes:
>
> > On Mon, 2013-12-30 at 15:31 +0100, Andreas Schwab wrote:
> >> GCC 4.8 now generates out-of-line vr save/restore functions when
> >> optimizing for size. They are needed for the raid6 altivec support.
> >
> > It looks like they're identical for 32 & 64-bit ?
>
> They use different temporary registers and calling conventions (no .opd
> for ppc64).
Yeah, sorry, you'd think I could spot the difference between r11 and r12.
cheers
prev parent reply other threads:[~2014-01-09 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 14:31 [PATCH] powerpc: add vr save/restore functions Andreas Schwab
2014-01-08 4:18 ` Michael Ellerman
2014-01-08 9:54 ` Andreas Schwab
2014-01-09 0:09 ` Michael Ellerman [this message]
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=1389226195.25505.3.camel@concordia \
--to=michael@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=schwab@linux-m68k.org \
/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 NNTP newsgroup(s).