From: Ken Matsui <kmatsui@cs.washington.edu>
To: gcc-patches@gcc.gnu.org
Cc: libstdc++@gcc.gnu.org, Ken Matsui <kmatsui@cs.washington.edu>
Subject: [PATCH 2/2] libstdc++: use new built-in trait __is_volatile
Date: Wed, 22 Mar 2023 16:41:34 -0700 [thread overview]
Message-ID: <20230322234134.14578-2-kmatsui@cs.washington.edu> (raw)
In-Reply-To: <20230322234134.14578-1-kmatsui@cs.washington.edu>
This patch lets libstdc++ use new built-in trait __is_volatile.
libstdc++-v3/ChangeLog:
* include/std/type_traits (is_volatile): Use __is_volatile built-in
trait.
---
libstdc++-v3/include/std/type_traits | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/libstdc++-v3/include/std/type_traits b/libstdc++-v3/include/std/type_traits
index 2bd607a8b8f..c50c8dba396 100644
--- a/libstdc++-v3/include/std/type_traits
+++ b/libstdc++-v3/include/std/type_traits
@@ -773,6 +773,12 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
: public true_type { };
/// is_volatile
+#if __has_builtin(__is_volatile)
+ template<typename _Tp>
+ struct is_volatile
+ : public __bool_constant<__is_volatile(_Tp)>
+ { };
+#else
template<typename>
struct is_volatile
: public false_type { };
@@ -780,6 +786,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
template<typename _Tp>
struct is_volatile<_Tp volatile>
: public true_type { };
+#endif
/// is_trivial
template<typename _Tp>
--
2.40.0
next prev parent reply other threads:[~2023-03-22 23:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 23:41 [PATCH 1/2] c++: implement __is_volatile built-in trait Ken Matsui
2023-03-22 23:41 ` Ken Matsui [this message]
2023-06-24 14:23 ` [PATCH v2 " Ken Matsui
2023-06-24 14:23 ` [PATCH v2 2/2] libstdc++: use new built-in trait __is_volatile Ken Matsui
2023-06-24 14:47 ` [PATCH v2 1/2] c++: implement __is_volatile built-in trait Ken Matsui
2023-07-08 5:18 ` [PATCH v3 " Ken Matsui
2023-07-08 5:18 ` [PATCH v3 2/2] libstdc++: use new built-in trait __is_volatile Ken Matsui
2023-09-01 13:00 ` [PING][PATCH " Ken Matsui
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=20230322234134.14578-2-kmatsui@cs.washington.edu \
--to=kmatsui@cs.washington.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.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).