From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Paul A. Clarke" <pc@us.ibm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/2] rs6000: Add support for _mm_minpos_epu16
Date: Wed, 2 Jun 2021 19:27:35 -0500 [thread overview]
Message-ID: <20210603002735.GO18427@gate.crashing.org> (raw)
In-Reply-To: <20210602221316.202627-2-pc@us.ibm.com>
Hi!
On Wed, Jun 02, 2021 at 05:13:15PM -0500, Paul A. Clarke wrote:
> Add a naive implementation of the subject x86 intrinsic to
> ease porting.
> +/* Return horizontal packed word minimum and its index in bits [15:0]
> + and bits [18:16] respectively. */
> +extern __inline __m128i __attribute__((__gnu_inline__, __always_inline__, __artificial__))
> +_mm_minpos_epu16 (__m128i __A)
> +{
> + union __u
> + {
> + __m128i __m;
> + __v8hu __uh;
> + };
> + union __u __u = { .__m = __A }, __r = { .__m = {0} };
> + unsigned short __ridx = 0;
> + unsigned short __rmin = __u.__uh[__ridx];
> + for (unsigned long __i = __ridx+1;
(spaces around the "+"?)
> + __i < sizeof (__u.__uh) / sizeof (__u.__uh[0]);
You should either use a macro for that, or just write "8" :-)
> + __i++)
> + {
> + if (__u.__uh[__i] < __rmin)
> + {
> + __rmin = __u.__uh[__i];
> + __ridx = __i;
> + }
> + }
> + __r.__uh[0] = __rmin;
> + __r.__uh[1] = __ridx;
> + return __r.__m;
> +}
This does not compute the index correctly for big endian (it needs to
walk from right to left for that). The construction of the return value
looks wrong as well.
Okay for trunk with that fixed. Thanks!
Segher
next prev parent reply other threads:[~2021-06-03 0:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 22:13 [PATCH 0/2] " Paul A. Clarke
2021-06-02 22:13 ` [PATCH 1/2] " Paul A. Clarke
2021-06-03 0:27 ` Segher Boessenkool [this message]
2021-06-03 17:59 ` Paul A. Clarke
2021-06-02 22:13 ` [PATCH 2/2] rs6000: Add test " Paul A. Clarke
2021-06-03 1:50 ` Segher Boessenkool
2021-06-03 18:01 ` Paul A. Clarke
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=20210603002735.GO18427@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=pc@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).