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 __remove_pointer
Date: Sat, 24 Jun 2023 03:12:10 -0700 [thread overview]
Message-ID: <20230624101210.57519-2-kmatsui@cs.washington.edu> (raw)
In-Reply-To: <20230624101210.57519-1-kmatsui@cs.washington.edu>
This patch lets libstdc++ use new built-in trait __remove_pointer.
libstdc++-v3/ChangeLog:
* include/std/type_traits (remove_pointer): Use __remove_pointer built-in trait.
Signed-off-by: Ken Matsui <kmatsui@cs.washington.edu>
---
libstdc++-v3/include/std/type_traits | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/libstdc++-v3/include/std/type_traits b/libstdc++-v3/include/std/type_traits
index 0e7a9c9c7f3..81497e2f3e1 100644
--- a/libstdc++-v3/include/std/type_traits
+++ b/libstdc++-v3/include/std/type_traits
@@ -2023,6 +2023,12 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
// Pointer modifications.
+ /// remove_pointer
+#if __has_builtin(__remove_pointer)
+ template<typename _Tp>
+ struct remove_pointer
+ { using type = __remove_pointer(_Tp); };
+#else
template<typename _Tp, typename>
struct __remove_pointer_helper
{ using type = _Tp; };
@@ -2031,11 +2037,11 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
struct __remove_pointer_helper<_Tp, _Up*>
{ using type = _Up; };
- /// remove_pointer
template<typename _Tp>
struct remove_pointer
: public __remove_pointer_helper<_Tp, __remove_cv_t<_Tp>>
{ };
+#endif
template<typename _Tp, typename = void>
struct __add_pointer_helper
--
2.41.0
next prev parent reply other threads:[~2023-06-24 10:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 12:21 [PATCH 1/2] c++: implement __remove_pointer built-in trait Ken Matsui
2023-06-15 12:21 ` [PATCH 2/2] libstdc++: use new built-in trait __remove_pointer Ken Matsui
2023-06-17 12:35 ` [PATCH 1/2] c++: implement __remove_pointer built-in trait Ken Matsui
2023-06-20 13:20 ` Ken Matsui
2023-06-20 15:21 ` Patrick Palka
2023-06-24 10:07 ` Ken Matsui
2023-06-24 10:12 ` Ken Matsui
2023-06-24 10:12 ` Ken Matsui [this message]
2023-07-08 5:29 ` [PATCH v2 " Ken Matsui
2023-07-08 5:29 ` [PATCH v2 2/2] libstdc++: use new built-in trait __remove_pointer Ken Matsui
2023-07-12 10:20 ` Jonathan Wakely
2023-09-04 15:00 ` [PING][PATCH v2 1/2] c++: implement __remove_pointer built-in trait Ken Matsui
-- strict thread matches above, loose matches on Subject: below --
2023-03-20 22:22 [PATCH " Ken Matsui
2023-03-20 22:22 ` [PATCH 2/2] libstdc++: use new built-in trait __remove_pointer 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=20230624101210.57519-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).