From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 3/3] riscv: add the predefines for the extensions
Date: Wed, 8 Jul 2020 23:48:09 +0200 [thread overview]
Message-ID: <20200708214810.56214-4-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20200708214810.56214-1-luc.vanoostenryck@gmail.com>
The RISC-V architecture has some predefined macros
to specify which extensions are supported.
So, now that these extensions are known via the '-march'
options, add the corresponding predefines.
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
target-riscv.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/target-riscv.c b/target-riscv.c
index 9431ebc9cabb..e7f2b03b821b 100644
--- a/target-riscv.c
+++ b/target-riscv.c
@@ -99,6 +99,25 @@ static void predefine_riscv(const struct target *self)
predefine("__riscv", 1, "1");
predefine("__riscv_xlen", 1, "%d", ptr_ctype.bit_size);
+ if (riscv_flags & RISCV_ATOMIC)
+ predefine("__riscv_atomic", 1, "1");
+ if (riscv_flags & RISCV_COMP)
+ predefine("__riscv_compressed", 1, "1");
+ if (riscv_flags & RISCV_DIV)
+ predefine("__riscv_div", 1, "1");
+ if (riscv_flags & RISCV_EMBD)
+ predefine("__riscv_32e", 1, "1");
+ if (riscv_flags & RISCV_FPU)
+ predefine("__riscv_flen", 1, "%d", (riscv_flags & RISCV_DOUBLE) ? 64 : 32);
+ if (riscv_flags & RISCV_FDIV)
+ predefine("__riscv_fdiv", 1, "1");
+ if (riscv_flags & RISCV_FDIV)
+ predefine("__riscv_fsqrt", 1, "1");
+ if (riscv_flags & RISCV_MUL)
+ predefine("__riscv_mul", 1, "1");
+ if ((riscv_flags & RISCV_MUL) && (riscv_flags & RISCV_DIV))
+ predefine("__riscv_muldiv", 1, "1");
+
if (cmodel)
predefine_strong("__riscv_cmodel_%s", cmodel);
}
--
2.27.0
prev parent reply other threads:[~2020-07-08 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 21:48 [PATCH 0/3] teach sparse about the '-march' for RISC-V Luc Van Oostenryck
2020-07-08 21:48 ` [PATCH 1/3] arch: teach sparse about the '-march' option Luc Van Oostenryck
2020-07-08 21:48 ` [PATCH 2/3] riscv: parse '-march=....' Luc Van Oostenryck
2020-07-08 21:48 ` Luc Van Oostenryck [this message]
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=20200708214810.56214-4-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.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 NNTP newsgroup(s).