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/is_unsigned)] libstdc++: use new built-in trait __is_unsigned
Date: Sat,  8 Jul 2023 05:54:09 +0000 (GMT)	[thread overview]
Message-ID: <20230708055409.B6FD93858D39@sourceware.org> (raw)

https://gcc.gnu.org/g:9c1ac3067379c3d2e8021969045843d68ea95f3b

commit 9c1ac3067379c3d2e8021969045843d68ea95f3b
Author: Ken Matsui <kmatsui@gcc.gnu.org>
Date:   Tue Mar 21 09:58:00 2023 -0700

    libstdc++: use new built-in trait __is_unsigned
    
    This patch lets libstdc++ use new built-in trait __is_unsigned.
    
    libstdc++-v3/ChangeLog:
    
            * include/std/type_traits (is_unsigned): Use __is_unsigned built-in
            trait.
    
    Signed-off-by: Ken Matsui <kmatsui@gcc.gnu.org>

Diff:
---
 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 0e7a9c9c7f3..c56684d7bd8 100644
--- a/libstdc++-v3/include/std/type_traits
+++ b/libstdc++-v3/include/std/type_traits
@@ -884,10 +884,17 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
     { };
 
   /// is_unsigned
+#if __has_builtin(__is_unsigned)
+  template<typename _Tp>
+    struct is_unsigned
+    : public __bool_constant<__is_unsigned(_Tp)>
+    { };
+#else
   template<typename _Tp>
     struct is_unsigned
     : public __and_<is_arithmetic<_Tp>, __not_<is_signed<_Tp>>>::type
     { };
+#endif
 
   /// @cond undocumented
   template<typename _Tp, typename _Up = _Tp&&>

                 reply	other threads:[~2023-07-08  5:54 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=20230708055409.B6FD93858D39@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: 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).