public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Ken Matsui <kmatsui@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc(refs/users/kmatsui/heads/remove_pointer)] libstdc++: use new built-in trait __remove_pointer Date: Sat, 8 Jul 2023 05:28:56 +0000 (GMT) [thread overview] Message-ID: <20230708052856.13C3C38582BD@sourceware.org> (raw) https://gcc.gnu.org/g:811b961b748b7a1d6dbc4bedf3ae7400ebcc0584 commit 811b961b748b7a1d6dbc4bedf3ae7400ebcc0584 Author: Ken Matsui <kmatsui@gcc.gnu.org> Date: Mon Mar 20 14:05:48 2023 -0700 libstdc++: use new built-in trait __remove_pointer 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@gcc.gnu.org> Diff: --- 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
reply other threads:[~2023-07-08 5:28 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=20230708052856.13C3C38582BD@sourceware.org \ --to=kmatsui@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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: linkBe 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).