From: Conor Dooley <conor@kernel.org>
To: linux-sparse@vger.kernel.org
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
luc.vanoostenryck@gmail.com, palmer@dabbelt.com,
linux-riscv@lists.infradead.org
Subject: [PATCH v1] RISC-V: Add basic support for the vector extension
Date: Mon, 6 Mar 2023 22:23:22 +0000 [thread overview]
Message-ID: <20230306222321.1992900-1-conor@kernel.org> (raw)
From: Conor Dooley <conor.dooley@microchip.com>
I've started hitting this in CI while testing Andy's vector enablement
series. I'm not entirely sure if there is more to do here, other than
squeezing in the duplicate of what has been done for other extensions.
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
This is based on top of patches already on the sparse list, adding
support for some multi-letter extensions for RISC-V:
https://lore.kernel.org/linux-sparse/20220811033138.20676-1-palmer@rivosinc.com/
https://lore.kernel.org/linux-sparse/20220811052957.16634-1-palmer@rivosinc.com/
CC: luc.vanoostenryck@gmail.com
CC: palmer@dabbelt.com
CC: linux-sparse@vger.kernel.org
CC: linux-riscv@lists.infradead.org
---
target-riscv.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/target-riscv.c b/target-riscv.c
index 8338d7a6..c8282814 100644
--- a/target-riscv.c
+++ b/target-riscv.c
@@ -21,6 +21,7 @@
#define RISCV_ZIFENCEI (1 << 11)
#define RISCV_ZICBOM (1 << 12)
#define RISCV_ZIHINTPAUSE (1 << 13)
+#define RISCV_VECTOR (1 << 14)
static unsigned int riscv_flags;
@@ -41,6 +42,7 @@ static void parse_march_riscv(const char *arg)
{ "f", RISCV_FLOAT|RISCV_FDIV|RISCV_ZICSR },
{ "d", RISCV_DOUBLE|RISCV_FDIV|RISCV_ZICSR },
{ "c", RISCV_COMP },
+ { "v", RISCV_VECTOR },
{ "_zicsr", RISCV_ZICSR },
{ "_zifencei", RISCV_ZIFENCEI },
{ "_zicbom", RISCV_ZICBOM },
@@ -147,6 +149,8 @@ static void predefine_riscv(const struct target *self)
predefine("__riscv_zicbom", 1, "1");
if (riscv_flags & RISCV_ZIHINTPAUSE)
predefine("__riscv_zihintpause", 1, "1");
+ if (riscv_flags & RISCV_VECTOR)
+ predefine("__riscv_vector", 1, "1");
if (cmodel)
predefine_strong("__riscv_cmodel_%s", cmodel);
--
2.39.2
next reply other threads:[~2023-03-06 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 22:23 Conor Dooley [this message]
2023-03-06 22:29 ` [PATCH v1] RISC-V: Add basic support for the vector extension Palmer Dabbelt
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=20230306222321.1992900-1-conor@kernel.org \
--to=conor@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@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).