From: Kito Cheng <kito.cheng@gmail.com>
To: Philipp Tomsich <ptomsich@ventanamicro.com>
Cc: "Christoph Muellner" <cmuellner@ventanamicro.com>,
"Andrew Waterman" <andrew@sifive.com>,
"Sinan Lin" <sinan@isrc.iscas.ac.cn>, jiawei <jiawei@iscas.ac.cn>,
"Tsukasa OI" <research_trasio@irq.a4lg.com>,
wuwei2016@iscas.ac.cn, "GCC Patches" <gcc-patches@gcc.gnu.org>,
yulong@nj.iscas.ac.cn, 廖仕华 <shihua@iscas.ac.cn>
Subject: Re: [PATCH 3/3] RISC-V:Cache Management Operation instructions testcases
Date: Fri, 18 Mar 2022 18:37:11 +0800 [thread overview]
Message-ID: <CA+yXCZCuQCa1zAFj6XoNu+jXa-5RAA9xy2F4c+BDanD4Aga8yw@mail.gmail.com> (raw)
In-Reply-To: <CABGf_WM-XQyCEg1B=6kRMa0Vb+rEGKYk+gTSxnen-T4uHUjJ8A@mail.gmail.com>
> You meant cbo_zero, right?
> CMO was only the task-group name, but the extensions ended up having "cbo"
> in their name…
Yeah, named with an extension name makes more sense, thank you for
pointing that out.
Either __builtin_riscv_cbo_zero or __builtin_riscv_zicboz_cbo_zero is
fine to me since I expect those builtin are used for compiler internal
only, and used to implement intrinsics in future.
next prev parent reply other threads:[~2022-03-18 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 2:49 [PATCH 0/3] RISC-V: Add Ratified Cache Management Operation ISA Extensions yulong
2022-03-04 2:49 ` [PATCH 1/3] RISC-V: Add mininal support for Zicbo[mzp] yulong
2022-03-04 2:49 ` [PATCH 2/3] RISC-V:Cache Management Operation instructions yulong
2022-03-04 2:49 ` [PATCH 3/3] RISC-V:Cache Management Operation instructions testcases yulong
2022-03-18 6:58 ` Kito Cheng
2022-03-18 10:15 ` Philipp Tomsich
2022-03-18 10:37 ` Kito Cheng [this message]
2022-03-25 6:20 [PATCH 0/3] RISC-V: Add Ratified Cache Management Operation ISA Extensions yulong
2022-03-25 6:20 ` [PATCH 3/3] RISC-V:Cache Management Operation instructions testcases yulong
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=CA+yXCZCuQCa1zAFj6XoNu+jXa-5RAA9xy2F4c+BDanD4Aga8yw@mail.gmail.com \
--to=kito.cheng@gmail.com \
--cc=andrew@sifive.com \
--cc=cmuellner@ventanamicro.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiawei@iscas.ac.cn \
--cc=ptomsich@ventanamicro.com \
--cc=research_trasio@irq.a4lg.com \
--cc=shihua@iscas.ac.cn \
--cc=sinan@isrc.iscas.ac.cn \
--cc=wuwei2016@iscas.ac.cn \
--cc=yulong@nj.iscas.ac.cn \
/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).