From: Shiqi Zhang <shiqi@isrc.iscas.ac.cn>
To: libc-alpha@sourceware.org
Cc: schwab@linux-m68k.org, richard.henderson@linaro.org,
joseph@codesourcery.com, Shiqi Zhang <shiqi@isrc.iscas.ac.cn>
Subject: [PATCH v3] riscv: Add macros for FPUCW/fcsr in fpu_control.h
Date: Thu, 6 Apr 2023 01:51:09 +0800 [thread overview]
Message-ID: <20230405175108.17815-1-shiqi@isrc.iscas.ac.cn> (raw)
Add macros for rounding modes and accrued exception flags in order to
make controlling fcsr easier for users.
Reference: RISC-V Unprivileged Spec v20191213, Section 11.2: Figure 11.2, Table 11.1 & 11.2
---
Changed naming of rounding modes to make it more consistent across
architectures.
v2: https://sourceware.org/pipermail/libc-alpha/2023-February/145482.html
v1: https://sourceware.org/pipermail/libc-alpha/2023-February/145474.html
Regards,
Shiqi Zhang
sysdeps/riscv/fpu_control.h | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/sysdeps/riscv/fpu_control.h b/sysdeps/riscv/fpu_control.h
index c33798c6bb..5d36f96984 100644
--- a/sysdeps/riscv/fpu_control.h
+++ b/sysdeps/riscv/fpu_control.h
@@ -36,6 +36,20 @@ extern fpu_control_t __fpu_control;
# define _FPU_DEFAULT 0
# define _FPU_IEEE _FPU_DEFAULT
+/* FPU rounding modes */
+# define _FPU_RC_NEAREST (0 << 5)
+# define _FPU_RC_ZERO (1 << 5)
+# define _FPU_RC_DOWN (2 << 5)
+# define _FPU_RC_UP (3 << 5)
+# define _FPU_RC_NEARESTFROMZERO (4 << 5)
+
+/* FPU accrued exception flags */
+# define _FPU_EXCEPT_NV (1 << 4)
+# define _FPU_EXCEPT_DZ (1 << 3)
+# define _FPU_EXCEPT_OF (1 << 2)
+# define _FPU_EXCEPT_UF (1 << 1)
+# define _FPU_EXCEPT_NX (1 << 0)
+
/* Type of the control word. */
typedef unsigned int fpu_control_t __attribute__ ((__mode__ (__SI__)));
--
2.40.0
reply other threads:[~2023-04-05 17:52 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=20230405175108.17815-1-shiqi@isrc.iscas.ac.cn \
--to=shiqi@isrc.iscas.ac.cn \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=richard.henderson@linaro.org \
--cc=schwab@linux-m68k.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).