From: Jens Gustedt <Jens.Gustedt@inria.fr>
To: musl@lists.openwall.com
Subject: [musl] [C23 feature tests 3/6] C23: add a feature test for the [u]int128_t
Date: Wed, 3 May 2023 13:40:00 +0200 [thread overview]
Message-ID: <c888814b01965f6885b03819c0cb9be00d4f5800.1684922674.git.Jens.Gustedt@inria.fr> (raw)
In-Reply-To: <cover.1684922674.git.Jens.Gustedt@inria.fr>
---
include/features.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/include/features.h b/include/features.h
index 05abcadc..4083436d 100644
--- a/include/features.h
+++ b/include/features.h
@@ -61,4 +61,11 @@
#define __has_VA_OPT1(...) __has_VA_OPT2(__VA_OPT__(,) 1, 0,)
#define __has_VA_OPT __has_VA_OPT1(C23)
+// If the platform supports the 128 integer type and has _BitInt(N)
+// support where N large enough (all C23 compiler should have the
+// latter)
+#if __SIZEOF_INT128__ && (__BITINT_MAXWIDTH__ >= 128)
+#define __has_int128_t 1
+#endif
+
#endif
--
2.34.1
next prev parent reply other threads:[~2023-05-24 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 10:04 [musl] [C23 feature tests 0/6] tests needed for C23 interfaces Jens Gustedt
2023-05-03 9:44 ` [musl] [C23 feature tests 1/6] C23: provide fallbacks for the use of C attributes Jens Gustedt
2023-05-03 11:26 ` [musl] [C23 feature tests 2/6] C23: add a feature test for the __VA_OPT__ feature Jens Gustedt
2023-05-03 11:40 ` Jens Gustedt [this message]
2023-05-09 15:27 ` [musl] [C23 feature tests 6/6] C23: add an internal interface for the new unsequenced attribute Jens Gustedt
2023-05-10 12:48 ` [musl] [C23 feature tests 5/6] add a `__inline_or_static` macro for pre-C99 compilers Jens Gustedt
2023-05-10 12:57 ` [musl] [C23 feature tests 4/6] Add a feature test for the _BitInt types Jens Gustedt
2023-05-24 13:58 ` [musl] [C23 feature tests 0/6] tests needed for C23 interfaces Rich Felker
2023-05-24 14:11 ` Jₑₙₛ Gustedt
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=c888814b01965f6885b03819c0cb9be00d4f5800.1684922674.git.Jens.Gustedt@inria.fr \
--to=jens.gustedt@inria.fr \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).