From: Segher Boessenkool <segher@kernel.crashing.org>
To: Bill Seurer <seurer@linux.vnet.ibm.com>
Cc: David Edelsohn <dje.gcc@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, rs6000] Add support for int versions of vec_adde
Date: Fri, 08 Apr 2016 14:50:00 -0000 [thread overview]
Message-ID: <20160408145043.GA26837@gate.crashing.org> (raw)
In-Reply-To: <5706CB5E.8010904@linux.vnet.ibm.com>
Hi Bill,
On Thu, Apr 07, 2016 at 04:04:30PM -0500, Bill Seurer wrote:
> On 04/05/16 21:27, David Edelsohn wrote:
> >On Tue, Apr 5, 2016 at 3:36 PM, Bill Seurer <seurer@linux.vnet.ibm.com>
> >> * config/rs6000/rs6000-c.c (altivec_overloaded_builtins,
> >> altivec_resolve_overloaded_builtin): Remove
> >> ALTIVEC_BUILTIN_VEC_ADDE
> >> from altivec_overloaded_builtins structure. Add support for it
> >> to
> >> altivec_resolve_overloaded_builtin function.
A total nit, but... If you change one thing in one places, and another
in another, put them in the changelog separately.
> >>+ /* for {un}signed ints,
> >>+ vec_adde (va, vb, carryv) == vec_add (vec_add (va, vb),
> >>carryv) */
> >
> >Same.
Also sentences start with a capital letter.
What is the definition of the builtin? The machine insn does
va + vb + (carryv & 1); your implementation skips the AND.
> >>--- gcc/testsuite/gcc.target/powerpc/vec-adde-int128.c (revision 0)
> >>+++ gcc/testsuite/gcc.target/powerpc/vec-adde-int128.c (working copy)
> >>@@ -0,0 +1,78 @@
> >>+/* { dg-do run { target { powerpc64le-*-* } } } */
Will powerpc64 (i.e. BE) not work?
Segher
next prev parent reply other threads:[~2016-04-08 14:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 19:36 Bill Seurer
2016-04-06 2:27 ` David Edelsohn
2016-04-07 21:04 ` Bill Seurer
2016-04-08 14:50 ` Segher Boessenkool [this message]
2016-04-08 16:21 ` Bill Seurer
2016-04-13 14:47 ` Bill Seurer
2016-04-13 15:59 ` Bill Seurer
2016-04-13 16:44 ` David Edelsohn
2016-05-02 13:38 ` Andreas Schwab
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=20160408145043.GA26837@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=seurer@linux.vnet.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).