From: David Edelsohn <dje.gcc@gmail.com>
To: Richard Henderson <rth@redhat.com>
Cc: Richard Henderson <rth@twiddle.net>,
Eric Botcazou <ebotcazou@adacore.com>,
gcc-patches@gcc.gnu.org, meissner@linux.vnet.ibm.com
Subject: Re: [PATCH 3/3] rs6000: Rewrite sync patterns for atomic; expand early.
Date: Tue, 12 Jun 2012 23:47:00 -0000 [thread overview]
Message-ID: <CAGWvny=GNcdty9mZqYe69EW_7OVO=b3uEyQUWTmO5HGocCKwhw@mail.gmail.com> (raw)
In-Reply-To: <4FD746DB.5040408@redhat.com>
On Tue, Jun 12, 2012 at 9:40 AM, Richard Henderson <rth@redhat.com> wrote:
>> I like your suggestion, but the PowerPC developer community does not
>> uniformly appreciate that behavior.
>
> Surely there's a difference between gratuitously using fp registers
> and that being the *only* way to implement a particular operation...
Should Altivec and SSE be used for TImode, and AVX for OImode?
- David
next prev parent reply other threads:[~2012-06-12 23:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 11:07 [PATCH 0/3] Conversion to __atomic builtins Richard Henderson
2011-11-12 11:45 ` [PATCH 2/3] ppc-linux: Fix call to _Unwind_SetGRPtr Richard Henderson
2011-11-12 13:23 ` [PATCH 3/3] rs6000: Rewrite sync patterns for atomic; expand early Richard Henderson
2011-11-14 21:57 ` David Edelsohn
2012-06-09 12:47 ` Eric Botcazou
2012-06-09 16:40 ` Richard Henderson
2012-06-12 2:30 ` David Edelsohn
2012-06-12 13:56 ` Richard Henderson
2012-06-12 17:46 ` Mike Stump
2012-06-12 23:47 ` David Edelsohn [this message]
2012-06-13 15:27 ` Richard Henderson
2012-06-12 15:58 ` Richard Henderson
2012-06-12 23:16 ` David Edelsohn
2012-06-13 8:47 ` Richard Guenther
2012-06-13 15:41 ` Richard Henderson
2011-11-12 13:47 ` [PATCH 1/3] rs6000: fix*_trunc insns use nonimmediate_operand Richard Henderson
2011-11-12 15:59 ` [PATCH 0/3] Conversion to __atomic builtins David Edelsohn
2011-11-14 22:43 ` David Edelsohn
2011-11-15 6:01 ` Richard Henderson
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='CAGWvny=GNcdty9mZqYe69EW_7OVO=b3uEyQUWTmO5HGocCKwhw@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@linux.vnet.ibm.com \
--cc=rth@redhat.com \
--cc=rth@twiddle.net \
/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).