public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: hongtao Liu <liuhongt@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-581] recognize bzhi pattern when there's zero_extendsidi.
Date: Wed, 18 May 2022 02:58:19 +0000 (GMT)	[thread overview]
Message-ID: <20220518025819.F1C373858D3C@sourceware.org> (raw)

https://gcc.gnu.org/g:102237c9f2f2667eb73cb5473bd3a9a97296a414

commit r13-581-g102237c9f2f2667eb73cb5473bd3a9a97296a414
Author: liuhongt <hongtao.liu@intel.com>
Date:   Thu Apr 28 15:30:06 2022 +0800

    recognize bzhi pattern when there's zero_extendsidi.
    
    backend has
    
    16550(define_insn "*bmi2_bzhi_<mode>3_2"
    16551  [(set (match_operand:SWI48 0 "register_operand" "=r")
    16552        (and:SWI48
    16553          (plus:SWI48
    16554            (ashift:SWI48 (const_int 1)
    16555                          (match_operand:QI 2 "register_operand" "r"))
    16556            (const_int -1))
    16557          (match_operand:SWI48 1 "nonimmediate_operand" "rm")))
    16558   (clobber (reg:CC FLAGS_REG))]
    16559  "TARGET_BMI2"
    16560  "bzhi\t{%<k>2, %1, %0|%0, %1, %<k>2}"
    16561  [(set_attr "type" "bitmanip")
    16562   (set_attr "prefix" "vex")
    16563   (set_attr "mode" "<MODE>")])
    
    But there's extra zero_extend in pattern match.
    
    424Failed to match this instruction:
    425(parallel [
    426        (set (reg:DI 90)
    427            (zero_extend:DI (and:SI (plus:SI (ashift:SI (const_int 1 [0x1])
    428                            (subreg:QI (reg:SI 98) 0))
    429                        (const_int -1 [0xffffffffffffffff]))
    430                    (subreg:SI (reg:DI 95) 0))))
    431        (clobber (reg:CC 17 flags))
    432    ])
    
    Add new define_insn for it.
    
    gcc/ChangeLog:
    
            PR target/104375
            * config/i386/i386.md (*bmi2_bzhi_zero_extendsidi_4): New
            define_insn.
    
    gcc/testsuite/ChangeLog:
    
            * gcc.target/i386/pr104375.c: New test.

Diff:
---
 gcc/config/i386/i386.md                  | 16 ++++++++++++++++
 gcc/testsuite/gcc.target/i386/pr104375.c |  9 +++++++++
 2 files changed, 25 insertions(+)

diff --git a/gcc/config/i386/i386.md b/gcc/config/i386/i386.md
index 76bb56542da..80fc6c903eb 100644
--- a/gcc/config/i386/i386.md
+++ b/gcc/config/i386/i386.md
@@ -16652,6 +16652,22 @@
    (set_attr "prefix" "vex")
    (set_attr "mode" "<MODE>")])
 
+(define_insn "*bmi2_bzhi_zero_extendsidi_4"
+  [(set (match_operand:DI 0 "register_operand" "=r")
+	(zero_extend:DI
+	  (and:SI
+	    (plus:SI
+	      (ashift:SI (const_int 1)
+			 (match_operand:QI 2 "register_operand" "r"))
+	      (const_int -1))
+	    (match_operand:SI 1 "nonimmediate_operand" "rm"))))
+   (clobber (reg:CC FLAGS_REG))]
+  "TARGET_64BIT && TARGET_BMI2"
+  "bzhi\t{%q2, %q1, %q0|%q0, %q1, %q2}"
+  [(set_attr "type" "bitmanip")
+   (set_attr "prefix" "vex")
+   (set_attr "mode" "DI")])
+
 (define_insn "bmi2_pdep_<mode>3"
   [(set (match_operand:SWI48 0 "register_operand" "=r")
         (unspec:SWI48 [(match_operand:SWI48 1 "register_operand" "r")
diff --git a/gcc/testsuite/gcc.target/i386/pr104375.c b/gcc/testsuite/gcc.target/i386/pr104375.c
new file mode 100644
index 00000000000..5c9f511da5c
--- /dev/null
+++ b/gcc/testsuite/gcc.target/i386/pr104375.c
@@ -0,0 +1,9 @@
+#/* { dg-do compile { target { ! ia32 } } } */
+/* { dg-options "-mbmi2 -O2" } */
+/* { dg-final { scan-assembler-times {(?n)shrx[\t ]+} 1 } } */
+/* { dg-final { scan-assembler-times {(?n)bzhi[\t ]+} 1 } } */
+
+unsigned long long bextr_u64(unsigned long long w, unsigned off, unsigned int len)
+{
+    return (w >> off) & ((1U << len) - 1U);
+}


                 reply	other threads:[~2022-05-18  2:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220518025819.F1C373858D3C@sourceware.org \
    --to=liuhongt@gcc.gnu.org \
    --cc=gcc-cvs@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).