public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-1081] xtensa: Make use of BALL/BNALL instructions
Date: Tue, 14 Jun 2022 00:30:20 +0000 (GMT)	[thread overview]
Message-ID: <20220614003020.97A80384600C@sourceware.org> (raw)

https://gcc.gnu.org/g:70ce04ca353bb0cda8321b91a77c2477e26d339b

commit r13-1081-g70ce04ca353bb0cda8321b91a77c2477e26d339b
Author: Takayuki 'January June' Suwa <jjsuwa_sys3175@yahoo.co.jp>
Date:   Thu May 27 19:04:12 2021 +0900

    xtensa: Make use of BALL/BNALL instructions
    
    In Xtensa ISA, there is no single machine instruction that calculates unary
    bitwise negation, but a few similar fused instructions are exist:
    
      "BALL  Ax, Ay, label"  // if ((~Ax & Ay) == 0) goto label;
      "BNALL Ax, Ay, label"  // if ((~Ax & Ay) != 0) goto label;
    
    These instructions have never been emitted before, but it seems no reason not
    to make use of them.
    
    gcc/ChangeLog:
    
            * config/xtensa/xtensa.md (*masktrue_bitcmpl): New insn pattern.
    
    gcc/testsuite/ChangeLog:
    
            * gcc.target/xtensa/BALL-BNALL.c: New.

Diff:
---
 gcc/config/xtensa/xtensa.md                  | 21 ++++++++++++++++++
 gcc/testsuite/gcc.target/xtensa/BALL-BNALL.c | 33 ++++++++++++++++++++++++++++
 2 files changed, 54 insertions(+)

diff --git a/gcc/config/xtensa/xtensa.md b/gcc/config/xtensa/xtensa.md
index 449e4b24262..a4477e2207e 100644
--- a/gcc/config/xtensa/xtensa.md
+++ b/gcc/config/xtensa/xtensa.md
@@ -1628,6 +1628,27 @@
    (set_attr "mode"	"none")
    (set_attr "length"	"3")])
 
+(define_insn "*masktrue_bitcmpl"
+  [(set (pc)
+	(if_then_else (match_operator 3 "boolean_operator"
+			[(and:SI (not:SI (match_operand:SI 0 "register_operand" "r"))
+				 (match_operand:SI 1 "register_operand" "r"))
+			 (const_int 0)])
+		      (label_ref (match_operand 2 "" ""))
+		      (pc)))]
+  ""
+{
+  switch (GET_CODE (operands[3]))
+    {
+    case EQ:	return "ball\t%0, %1, %2";
+    case NE:	return "bnall\t%0, %1, %2";
+    default:	gcc_unreachable ();
+    }
+}
+  [(set_attr "type"	"jump")
+   (set_attr "mode"	"none")
+   (set_attr "length"	"3")])
+
 
 ;; Zero-overhead looping support.
 
diff --git a/gcc/testsuite/gcc.target/xtensa/BALL-BNALL.c b/gcc/testsuite/gcc.target/xtensa/BALL-BNALL.c
new file mode 100644
index 00000000000..ba61c6f371b
--- /dev/null
+++ b/gcc/testsuite/gcc.target/xtensa/BALL-BNALL.c
@@ -0,0 +1,33 @@
+/* { dg-do compile } */
+/* { dg-options "-O" } */
+
+extern void foo(void);
+
+void BNONE_test(int a, int b)
+{
+  if (a & b)
+    foo();
+}
+
+void BANY_test(int a, int b)
+{
+  if (!(a & b))
+    foo();
+}
+
+void BALL_test(int a, int b)
+{
+  if (~a & b)
+    foo();
+}
+
+void BNALL_test(int a, int b)
+{
+  if (!(~a & b))
+    foo();
+}
+
+/* { dg-final { scan-assembler-times "bnone" 1 } } */
+/* { dg-final { scan-assembler-times "bany" 1 } } */
+/* { dg-final { scan-assembler-times "ball" 1 } } */
+/* { dg-final { scan-assembler-times "bnall" 1 } } */


                 reply	other threads:[~2022-06-14  0:30 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=20220614003020.97A80384600C@sourceware.org \
    --to=jcmvbkbc@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).