From: Uros Bizjak <ubizjak@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Kirill Yukhin <kirill.yukhin@gmail.com>,
Thomas Schwinge <thomas@codesourcery.com>,
Andrew Senkevich <andrew.n.senkevich@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Biener <rguenther@suse.de>
Subject: Re: [PATCH] Add AVX512 k-mask intrinsics
Date: Thu, 26 Jan 2017 11:18:00 -0000 [thread overview]
Message-ID: <CAFULd4Z+EB-8i9wg=3Z8p1hqN1ceerUk3LtXcC9EDG_HfoBSQg@mail.gmail.com> (raw)
In-Reply-To: <20170126110054.GA1867@tucnak>
On Thu, Jan 26, 2017 at 12:00 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> On Thu, Jan 26, 2017 at 11:54:52AM +0100, Uros Bizjak wrote:
>> On Thu, Jan 26, 2017 at 11:51 AM, Jakub Jelinek <jakub@redhat.com> wrote:
>> > On Thu, Jan 26, 2017 at 02:44:56AM -0800, Kirill Yukhin wrote:
>> >> Hello Thomas,
>> >> On 26 Jan 10:14, Thomas Schwinge wrote:
>> >> > I see:
>> >> >
>> >> > {+FAIL: gcc.target/i386/avx512f-ktestw-2.c (test for excess errors)+}
>> >> > {+UNRESOLVED: gcc.target/i386/avx512f-ktestw-2.c compilation failed to produce executable+}
>> >> >
>> >> > ... because of:
>> >> >
>> >> > /tmp/ccjv3mX2.s: Assembler messages:
>> >> > /tmp/ccjv3mX2.s:26: Error: no such instruction: `ktestw %k1,%k0'
>> >> > compiler exited with status 1
>> >> Which version of gas do you use?
>> >> It should be OK since v2.25.
>> >
>> > It is weird, because the test already has:
>> > /* { dg-require-effective-target avx512f } */
>> > Perhaps if there are gas versions with partial avx512f support, we need
>> > to improve the avx512f effective target test.
>>
>> This is actually AVX512DQ instruction, please see [1], 3-509.
>>
>> [1] https://software.intel.com/sites/default/files/managed/ad/01/253666-sdm-vol-2a.pdf
>
> You're right. But then the tests should be named avx512dq-ktestw-{1,2}.c,
> should use -mavx512dq, avx512dq effective target etc. and indeed the
> intrinsics shouldn't be in avx512fintrin.h header, but dq, and should not be
> enabled for f, but only dq.
Yes, all this is needed to fix this oversight (and one more with
kaddw), as I proposed a couple of messages earlier.
Uros.
next prev parent reply other threads:[~2017-01-26 11:04 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 14:34 Uros Bizjak
2016-11-11 17:39 ` Andrew Senkevich
2016-11-11 17:50 ` Uros Bizjak
2016-11-11 17:56 ` Uros Bizjak
2016-11-11 18:23 ` Andrew Senkevich
2016-11-11 19:14 ` Uros Bizjak
2016-12-02 17:45 ` Andrew Senkevich
2016-12-02 18:31 ` Uros Bizjak
2016-12-05 14:59 ` Andrew Senkevich
2016-12-05 17:19 ` H.J. Lu
2016-12-14 19:33 ` Andrew Senkevich
2016-12-14 20:35 ` Uros Bizjak
[not found] ` <CAMXFM3vC-3bMgQaQ2bnjDU7oQMPdvhurzgOFftZHqzNXAw=WgA@mail.gmail.com>
2016-12-15 16:51 ` Uros Bizjak
2016-12-15 19:04 ` Andrew Senkevich
2016-12-16 12:45 ` Uros Bizjak
2017-01-16 22:30 ` Andrew Senkevich
2017-01-16 22:55 ` Jakub Jelinek
2017-01-17 11:05 ` Andrew Senkevich
2017-01-17 11:06 ` Uros Bizjak
2017-01-17 12:30 ` Kirill Yukhin
2017-01-17 13:03 ` Andrew Senkevich
2017-01-17 13:51 ` Jakub Jelinek
2017-01-18 12:48 ` Andrew Senkevich
2017-01-18 21:45 ` Uros Bizjak
2017-01-19 10:46 ` Kirill Yukhin
2017-01-19 16:45 ` Andrew Senkevich
2017-01-19 18:04 ` Kirill Yukhin
2017-01-20 13:41 ` Andrew Senkevich
2017-01-20 13:47 ` Uros Bizjak
2017-01-20 17:26 ` Kirill Yukhin
2017-01-20 20:07 ` Andrew Senkevich
2017-01-21 8:25 ` Richard Biener
2017-01-23 11:33 ` Kirill Yukhin
2017-01-26 9:38 ` Thomas Schwinge
2017-01-26 10:04 ` Uros Bizjak
2017-01-26 10:51 ` Kirill Yukhin
2017-01-26 10:54 ` Jakub Jelinek
2017-01-26 10:55 ` Uros Bizjak
2017-01-26 11:04 ` Jakub Jelinek
2017-01-26 11:18 ` Uros Bizjak [this message]
2017-01-26 11:53 ` Thomas Schwinge
2017-01-26 12:04 ` Kirill Yukhin
2017-01-26 12:17 ` Jakub Jelinek
2017-01-26 12:23 ` Kirill Yukhin
2017-01-17 8:12 ` Uros Bizjak
-- strict thread matches above, loose matches on Subject: below --
2016-11-11 14:14 Andrew Senkevich
2016-11-11 15:26 ` Marc Glisse
2016-11-11 18:28 ` Andrew Senkevich
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='CAFULd4Z+EB-8i9wg=3Z8p1hqN1ceerUk3LtXcC9EDG_HfoBSQg@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=andrew.n.senkevich@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=kirill.yukhin@gmail.com \
--cc=rguenther@suse.de \
--cc=thomas@codesourcery.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).