public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ken Matsui <kmatsui@cs.washington.edu>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	"libstdc++" <libstdc++@gcc.gnu.org>,
	 Ken Matsui <kmatsui@gcc.gnu.org>
Subject: [PING][PATCH v3 2/2] libstdc++: use new built-in trait __is_volatile
Date: Fri, 1 Sep 2023 06:00:00 -0700	[thread overview]
Message-ID: <CAML+3pUpen4qyEZuQO4Cx7Otds-TB=LwpZc6DyfQoZSdMim2FA@mail.gmail.com> (raw)
In-Reply-To: <20230708051825.64839-2-kmatsui@gcc.gnu.org>

Ping for the use of __is_volatile built-in.

Sincerely,
Ken Matsui

On Fri, Jul 7, 2023 at 10:19 PM Ken Matsui <kmatsui@gcc.gnu.org> wrote:
>
> 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.
>         (is_volatile_v): Likewise.
>
> Signed-off-by: Ken Matsui <kmatsui@gcc.gnu.org>
> ---
>  libstdc++-v3/include/std/type_traits | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
>
> diff --git a/libstdc++-v3/include/std/type_traits b/libstdc++-v3/include/std/type_traits
> index 0e7a9c9c7f3..db74b884b35 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>
> @@ -3214,10 +3221,16 @@ template <typename _Tp>
>    inline constexpr bool is_const_v = false;
>  template <typename _Tp>
>    inline constexpr bool is_const_v<const _Tp> = true;
> +
> +#if __has_builtin(__is_volatile)
> +template <typename _Tp>
> +  inline constexpr bool is_volatile_v = __is_volatile(_Tp);
> +#else
>  template <typename _Tp>
>    inline constexpr bool is_volatile_v = false;
>  template <typename _Tp>
>    inline constexpr bool is_volatile_v<volatile _Tp> = true;
> +#endif
>
>  template <typename _Tp>
>    inline constexpr bool is_trivial_v = __is_trivial(_Tp);
> --
> 2.41.0
>

      reply	other threads:[~2023-09-01 13:00 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 ` [PATCH 2/2] libstdc++: use new built-in trait __is_volatile Ken Matsui
2023-06-24 14:23 ` [PATCH v2 1/2] c++: implement __is_volatile built-in trait 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         ` Ken Matsui [this message]

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='CAML+3pUpen4qyEZuQO4Cx7Otds-TB=LwpZc6DyfQoZSdMim2FA@mail.gmail.com' \
    --to=kmatsui@cs.washington.edu \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely@redhat.com \
    --cc=kmatsui@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).