From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
Kito Cheng <kito.cheng@gmail.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Andrew Waterman <andrew@sifive.com>,
Jim Wilson <jim.wilson.gcc@gmail.com>,
Jeff Law <jeffreyalaw@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: [RFC PATCH v2 0/1] RISC-V: Add support for 'XVentanaCondOps' reusing 'Zicond' support
Date: Wed, 30 Aug 2023 22:54:56 +0000 [thread overview]
Message-ID: <cover.1693436086.git.research_trasio@irq.a4lg.com> (raw)
In-Reply-To: <2adcf40a405ec562076e5cdbc185ff3b7ddd48da.1693377796.git.research_trasio@irq.a4lg.com>
PATCH v1:
<https://gcc.gnu.org/pipermail/gcc-patches/2023-August/628786.html>
Changes: v1 -> v2
* Removed bogus opt2 pattern as pointed out in:
<https://gcc.gnu.org/pipermail/gcc-patches/2023-August/628867.html>
note that this is not in the ChangeLog expecting the patch above
applies first.
Tsukasa OI (1):
RISC-V: Add support for 'XVentanaCondOps' reusing 'Zicond' support
gcc/common/config/riscv/riscv-common.cc | 2 +
gcc/config/riscv/riscv-opts.h | 6 +++
gcc/config/riscv/riscv.cc | 4 +-
gcc/config/riscv/riscv.md | 2 +-
gcc/config/riscv/riscv.opt | 3 ++
gcc/config/riscv/zicond.md | 52 ++++++++++++-------
.../xventanacondops-primitiveSemantics-rv32.c | 45 ++++++++++++++++
.../xventanacondops-primitiveSemantics.c | 48 +++++++++++++++++
.../gcc.target/riscv/xventanacondops-xor-01.c | 14 +++++
9 files changed, 154 insertions(+), 22 deletions(-)
create mode 100644 gcc/testsuite/gcc.target/riscv/xventanacondops-primitiveSemantics-rv32.c
create mode 100644 gcc/testsuite/gcc.target/riscv/xventanacondops-primitiveSemantics.c
create mode 100644 gcc/testsuite/gcc.target/riscv/xventanacondops-xor-01.c
base-commit: 597b9ec69bca8acb7a3d65641c0a730de8b27ed4
--
2.42.0
next prev parent reply other threads:[~2023-08-30 22:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 6:44 [RFC PATCH] " Tsukasa OI
2023-08-30 22:54 ` Tsukasa OI [this message]
2023-08-30 22:54 ` [RFC PATCH v2 1/1] " Tsukasa OI
2023-09-05 12:10 ` [PATCH v3 0/1] " Tsukasa OI
2023-09-05 12:10 ` [PATCH v3 1/1] " Tsukasa OI
2023-09-06 0:17 ` Jeff Law
2023-09-06 2:33 ` Tsukasa OI
2023-09-06 3:07 ` Jeff Law
2023-09-06 3:16 ` Palmer Dabbelt
2023-09-06 5:47 ` [PATCH v4 0/1] " Tsukasa OI
2023-09-06 5:47 ` [PATCH v4 1/1] " Tsukasa OI
2023-09-06 14:04 ` Jeff Law
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=cover.1693436086.git.research_trasio@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=andrew@sifive.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=jim.wilson.gcc@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.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).