public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-2183] [RISCV] Move iterators from sync.md to iterators.md
Date: Wed, 24 Aug 2022 19:20:13 +0000 (GMT)	[thread overview]
Message-ID: <20220824192013.95C923852767@sourceware.org> (raw)

https://gcc.gnu.org/g:7770e0ad8f4bcd2c7852fa88eb7d5235f68a811d

commit r13-2183-g7770e0ad8f4bcd2c7852fa88eb7d5235f68a811d
Author: Andrew Pinski <apinski@marvell.com>
Date:   Fri Aug 12 00:44:16 2022 +0000

    [RISCV] Move iterators from sync.md to iterators.md
    
    Like the previous two patches this moves the iterators
    that are in sync.md to iterators.md.
    
    OK? build and tested for riscv64-linux-gnu.
    
    gcc/ChangeLog:
    
            * config/riscv/sync.md (any_atomic, atomic_optab): Move to ...
            * config/riscv/iterators.md: Here.

Diff:
---
 gcc/config/riscv/iterators.md | 7 +++++++
 gcc/config/riscv/sync.md      | 4 ----
 2 files changed, 7 insertions(+), 4 deletions(-)

diff --git a/gcc/config/riscv/iterators.md b/gcc/config/riscv/iterators.md
index cb57ac7cb7b..2d7223d8a8a 100644
--- a/gcc/config/riscv/iterators.md
+++ b/gcc/config/riscv/iterators.md
@@ -150,6 +150,9 @@
 (define_code_iterator any_lt [lt ltu])
 (define_code_iterator any_le [le leu])
 
+; atomics code iterator
+(define_code_iterator any_atomic [plus ior xor and])
+
 ; bitmanip code iterators
 (define_code_iterator bitmanip_bitwise [and ior])
 
@@ -204,6 +207,10 @@
 			(plus "add")
 			(minus "sub")])
 
+; atomics code attribute
+(define_code_attr atomic_optab
+  [(plus "add") (ior "or") (xor "xor") (and "and")])
+
 ; bitmanip code attributes
 (define_code_attr bitmanip_optab [(smin "smin")
 				  (smax "smax")
diff --git a/gcc/config/riscv/sync.md b/gcc/config/riscv/sync.md
index 86b41e6b00a..7deb290d9dc 100644
--- a/gcc/config/riscv/sync.md
+++ b/gcc/config/riscv/sync.md
@@ -27,10 +27,6 @@
   UNSPEC_MEMORY_BARRIER
 ])
 
-(define_code_iterator any_atomic [plus ior xor and])
-(define_code_attr atomic_optab
-  [(plus "add") (ior "or") (xor "xor") (and "and")])
-
 ;; Memory barriers.
 
 (define_expand "mem_thread_fence"

                 reply	other threads:[~2022-08-24 19:20 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=20220824192013.95C923852767@sourceware.org \
    --to=pinskia@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).