public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ken Matsui <kmatsui@cs.washington.edu>
To: gcc-patches@gcc.gnu.org
Cc: libstdc++@gcc.gnu.org, ppalka@redhat.com,
	Ken Matsui <kmatsui@cs.washington.edu>
Subject: [PATCH 2/2] libstdc++: use new built-in trait __add_const
Date: Tue, 21 Mar 2023 04:10:56 -0700	[thread overview]
Message-ID: <20230321111056.78121-2-kmatsui@cs.washington.edu> (raw)
In-Reply-To: <20230321111056.78121-1-kmatsui@cs.washington.edu>

This patch lets libstdc++ use new built-in trait __add_const.

libstdc++-v3/ChangeLog:

	* include/std/type_traits (add_const): Use __add_const built-in trait.
---
 libstdc++-v3/include/std/type_traits | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/libstdc++-v3/include/std/type_traits b/libstdc++-v3/include/std/type_traits
index 2bd607a8b8f..1ac75a928c3 100644
--- a/libstdc++-v3/include/std/type_traits
+++ b/libstdc++-v3/include/std/type_traits
@@ -1560,9 +1560,15 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
 #endif
 
   /// add_const
+#if __has_builtin(__add_const)
+  template<typename _Tp>
+    struct add_const
+    { using type = __add_const(_Tp); };
+#else
   template<typename _Tp>
     struct add_const
     { using type = _Tp const; };
+#endif
 
   /// add_volatile
   template<typename _Tp>
-- 
2.40.0


  reply	other threads:[~2023-03-21 11:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 11:10 [PATCH 1/2] c++: implement __add_const built-in trait Ken Matsui
2023-03-21 11:10 ` Ken Matsui [this message]
2023-03-21 11:20   ` [PATCH 2/2] libstdc++: use new built-in trait __add_const Marc Glisse
2023-03-21 11:24     ` Jonathan Wakely
2023-03-21 11:37       ` Ken Matsui
2023-03-21 11:26 ` [PATCH 1/2] c++: implement __add_const built-in trait Jonathan Wakely
2023-03-21 11:29   ` Jonathan Wakely

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=20230321111056.78121-2-kmatsui@cs.washington.edu \
    --to=kmatsui@cs.washington.edu \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=ppalka@redhat.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.
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).