public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Hongtao Liu <crazylht@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][AVX512]Lower AVX512 vector compare to AVX version when dest is vector
Date: Mon, 30 Nov 2020 09:38:03 -0700	[thread overview]
Message-ID: <15b623ef-bed1-0f00-c8e6-eb976d5f20a8@redhat.com> (raw)
In-Reply-To: <CAMZc-bzwug-9ni6iV55VSP4=WQ2mWcf_tVX6XKRUoEKiSOMZmg@mail.gmail.com>



On 11/16/20 8:10 PM, Hongtao Liu wrote:
> On Tue, Nov 17, 2020 at 8:05 AM Jeff Law <law@redhat.com> wrote:
>>
>> On 9/2/20 3:34 AM, Hongtao Liu via Gcc-patches wrote:
>>> Hi:
>>>   Add define_peephole2 to eliminate potential redundant conversion
>>> from mask to vector.
>>>   Bootstrap is ok, regression test is ok for i386/x86-64 backend.
>>>   Ok for trunk?
>>>
>>> gcc/ChangeLog:
>>>         PR target/96891
>>>         * config/i386/sse.md (VI_128_256): New mode iterator.
>>>         (define_peephole2): Lower avx512 vector compare to avx version
>>>         when dest is vector.
>>>
>>> gcc/testsuite/ChangeLog:
>>>
>>>         * gcc.target/i386/avx512bw-pr96891-1.c: New test.
>>>         * gcc.target/i386/avx512f-pr96891-1.c: New test.
>>>         * gcc.target/i386/avx512f-pr96891-2.c: New test.
>> Aren't these the two insns in question:
>>
>>
>> (insn 7 4 8 2 (set (reg:QI 86)
>>         (unspec:QI [
>>                 (reg:V8SF 90)
>>                 (reg:V8SF 89)
>>                 (const_int 2 [0x2])
>>             ] UNSPEC_PCMP)) "j.c":4:14 1911 {avx512vl_cmpv8sf3}
>>      (expr_list:REG_DEAD (reg:V8SF 90)
>>         (expr_list:REG_DEAD (reg:V8SF 89)
>>             (nil))))
>> (note 8 7 9 2 NOTE_INSN_DELETED)
>> (insn 9 8 14 2 (set (reg:V8SI 82 [ _2 ])
>>         (vec_merge:V8SI (const_vector:V8SI [
>>                     (const_int -1 [0xffffffffffffffff]) repeated x8
>>                 ])
>>             (const_vector:V8SI [
>>                     (const_int 0 [0]) repeated x8
>>                 ])
>>             (reg:QI 86))) "j.c":4:14 2705 {*avx512vl_cvtmask2dv8si}
>>      (expr_list:REG_DEAD (reg:QI 86)
>>         (nil)))
>>
>>
>> Note there's a data dependency between them.  insn 7 feeds insn 9.  When
>> there's a data dependency, combiner patterns are usually the better
>> choice than peepholes.  I think you'd be looking to match something
>> likethis (from the . combine dump):
>>
>> (set (reg:V8SI 82 [ _2 ])
>>     (vec_merge:V8SI (const_vector:V8SI [
>>                 (const_int -1 [0xffffffffffffffff]) repeated x8
>>             ])
>>         (const_vector:V8SI [
>>                 (const_int 0 [0]) repeated x8
>>             ])
>>         (unspec:QI [
>>                 (reg:V8SF 90)
>>                 (reg:V8SF 89)
>>                 (const_int 2 [0x2])
>>             ] UNSPEC_PCMP)))
>>
>>
>> Jeff
>>
> Yes, as discussed in [1], maybe it's better to refactor avx512 integer
> mask with VnBImode. Then unspec_pcmp could be dropped and simplify_rtx
> could handle vector comparison more effectively.
>
> [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97521#c4
Thanks for the pointer.   I didn't realize this patch was essentially
abandoned.

Jeff


  reply	other threads:[~2020-11-30 16:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02  9:34 Hongtao Liu
2020-09-02 12:20 ` H.J. Lu
2020-11-17  0:05 ` Jeff Law
2020-11-17  3:10   ` Hongtao Liu
2020-11-30 16:38     ` Jeff Law [this message]
2021-01-06  3:34       ` Hongtao Liu
2021-01-21 13:47         ` Jakub Jelinek

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=15b623ef-bed1-0f00-c8e6-eb976d5f20a8@redhat.com \
    --to=law@redhat.com \
    --cc=crazylht@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    /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).