From: Jakub Jelinek <jakub@redhat.com>
To: Allan Sandfeld Jensen <linux@carewolf.com>
Cc: gcc-patches@gcc.gnu.org, Uros Bizjak <ubizjak@gmail.com>
Subject: Re: [PATCH] [x86] Avoid builtins for SSE/AVX2 immidiate logical shifts
Date: Mon, 24 Apr 2017 08:38:00 -0000 [thread overview]
Message-ID: <20170424082553.GJ1809@tucnak> (raw)
In-Reply-To: <201704241002.40719.linux@carewolf.com>
On Mon, Apr 24, 2017 at 10:02:40AM +0200, Allan Sandfeld Jensen wrote:
> > That said, both the options I've mentioned above provide the same
> > advantages and don't have the disadvantages of pessimizing normal code.
> >
> What pessimizing? This produce the same or better code for all legal
> arguments. The only difference besides better generated code is that it allows
No. Have you really tried that?
> the intrinsics to be used incorrectly with non-literal arguments because we
> lack the C-extension for constexp to prevent that.
Consider e.g. -O2 -mavx2 -mtune=intel:
#include <x86intrin.h>
__m256i
foo (__m256i x, int s)
{
return (__m256i)__builtin_ia32_psllwi256 ((__v16hi)x, s);
}
__m256i
bar (__m256i x, int s)
{
return ((s & 0xff) < 16) ? (__m256i)((__v16hi)x << (s & 0xff)) : _mm256_setzero_si256 ();
}
The first one generates
movl %edi, %edi
vmovq %rdi, %xmm1
vpsllw %xmm1, %ymm0, %ymm0
ret
(because that is actually what the instruction does), the second one
movzbl %dil, %edi
cmpl $15, %edi
jg .L5
vmovq %rdi, %xmm1
vpsllw %xmm1, %ymm0, %ymm0
ret
.p2align 4,,7
.p2align 3
.L5:
vpxor %xmm0, %xmm0, %xmm0
ret
Jakub
next prev parent reply other threads:[~2017-04-24 8:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201704221338.46300.linux@carewolf.com>
2017-04-24 7:43 ` Allan Sandfeld Jensen
2017-04-24 7:47 ` Jakub Jelinek
2017-04-24 8:02 ` Allan Sandfeld Jensen
2017-04-24 8:25 ` Jakub Jelinek
2017-04-24 8:25 ` Allan Sandfeld Jensen
2017-04-24 8:38 ` Jakub Jelinek [this message]
2017-04-24 8:40 ` Allan Sandfeld Jensen
2017-04-24 8:54 ` Allan Sandfeld Jensen
2017-04-24 8:57 ` Jakub Jelinek
2017-04-24 14:43 ` Allan Sandfeld Jensen
2017-05-02 10:17 ` Jakub Jelinek
2017-05-02 11:22 ` Allan Sandfeld Jensen
2017-05-02 15:58 ` Marc Glisse
[not found] ` <201704241101.29634.linux@carewolf.com>
2017-04-24 9:38 ` Jakub Jelinek
2017-04-24 9:38 ` Allan Sandfeld Jensen
2017-04-24 9:17 Allan Sandfeld Jensen
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=20170424082553.GJ1809@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linux@carewolf.com \
--cc=ubizjak@gmail.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).