From: Uros Bizjak <ubizjak@gmail.com>
To: Kirill Yukhin <kirill.yukhin@gmail.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, i386, AVX-512] Update extract_even_odd w/ AVX-512BW insns.
Date: Thu, 08 Oct 2015 07:02:00 -0000 [thread overview]
Message-ID: <CAFULd4YzGH_geAxM_H8ShWiYPe2Y7D+wB75O8+SzHuzvffHYmg@mail.gmail.com> (raw)
In-Reply-To: <20151008051412.GB19437@msticlxl57.ims.intel.com>
On Thu, Oct 8, 2015 at 7:14 AM, Kirill Yukhin <kirill.yukhin@gmail.com> wrote:
> Hello,
> On 06 Oct 15:09, Kirill Yukhin wrote:
>> > > This caused:
>> > >
>> > > FAIL: gcc.target/i386/vect-perm-odd-1.c (test for excess errors)
>> > >
>> > > on gcc-5-branch.
>> > >
>> >
>> > vect-perm-odd-1.s: Assembler messages:
>> > vect-perm-odd-1.s:233: Error: operand type mismatch for `vpor'
>> > vect-perm-odd-1.s:240: Error: operand type mismatch for `vpor'
>> >
>> > vpor %zmm1, %zmm2, %zmm1
>> >
>> > It should be
>> >
>> > vporq %zmm1, %zmm2, %zmm1
>>
>> It looks like patch revealed issue w/ wrong `or' emit.
>> Patch of Alexander Fomin fixes it.
>>
>> I've backported it for gcc-5.
>>
>> Bootstrapped. Regtest in progress.
>> Is it ok for gcc-5 if regtesting pass?
> Regtesting pass.
>
> Is it ok for gcc-5-branch?
+/* { dg-options "-mavx512bw -O2 -ftree-vectorize" { target i?86-*-*
x86_64-*-* } } */
No need for target selector in gcc.target/i386 directory.
OK.
Thanks,
Uros.
next prev parent reply other threads:[~2015-10-08 7:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 11:12 Kirill Yukhin
2015-10-02 14:38 ` Kirill Yukhin
2015-10-06 11:05 ` H.J. Lu
2015-10-06 11:18 ` H.J. Lu
2015-10-06 12:10 ` Kirill Yukhin
2015-10-08 5:14 ` Kirill Yukhin
2015-10-08 7:02 ` Uros Bizjak [this message]
2015-10-03 10:49 Dominique d'Humières
2015-10-04 14:04 ` Uros Bizjak
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=CAFULd4YzGH_geAxM_H8ShWiYPe2Y7D+wB75O8+SzHuzvffHYmg@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=kirill.yukhin@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).