From: Jonathan Wakely <jwakely@redhat.com>
To: Ken Matsui <kmatsui@gcc.gnu.org>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH v4 4/4] libstdc++: Optimize is_compound trait performance
Date: Tue, 8 Aug 2023 21:33:11 +0100 [thread overview]
Message-ID: <CACb0b4n0JjbxrXFVexGcZ9s07LmcGCWzgRD5+QLRJDgtEvfAvw@mail.gmail.com> (raw)
In-Reply-To: <20230718074027.32270-4-kmatsui@gcc.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2302 bytes --]
On Tue, 18 Jul 2023 at 08:44, Ken Matsui via Libstdc++ <
libstdc++@gcc.gnu.org> wrote:
> This patch optimizes the performance of the is_compound trait by
> dispatching to the new __is_arithmetic built-in trait.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/type_traits (is_compound): Use __is_arithmetic
> built-in trait.
> (is_compound_v): Use is_fundamental_v instead.
>
> Signed-off-by: Ken Matsui <kmatsui@gcc.gnu.org>
> ---
> libstdc++-v3/include/std/type_traits | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/libstdc++-v3/include/std/type_traits
> b/libstdc++-v3/include/std/type_traits
> index cf24de2fcac..73d9a2b16fc 100644
> --- a/libstdc++-v3/include/std/type_traits
> +++ b/libstdc++-v3/include/std/type_traits
> @@ -702,9 +702,18 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
> { };
>
> /// is_compound
> +#if __has_builtin(__is_arithmetic)
> + template<typename _Tp>
> + struct is_compound
> + : public __bool_constant<!(__is_arithmetic(_Tp)
> + || is_void<_Tp>::value
> + || is_null_pointer<_Tp>::value)>
> + { };
> +#else
> template<typename _Tp>
> struct is_compound
> : public __not_<is_fundamental<_Tp>>::type { };
> +#endif
>
I think it would be simpler to just do this unconditionally (i.e. just a
single definition without using __has_builtin):
template<typename _Tp>
struct is_compound
: __bool_constant<!is_fundamental<_Tp>::value>
{ };
This still avoids instantiating __not_. If is_fundamental is much more
efficient now, then I think it's OK to instantiate it here. Otherwise we're
duplicating the logic for is_fundamental, and just giving ourselves more
code to maintain.
Nobody ever uses is_compound anyway!
> /// @cond undocumented
> template<typename _Tp>
> @@ -3234,7 +3243,7 @@ template <typename _Tp>
> template <typename _Tp>
> inline constexpr bool is_scalar_v = is_scalar<_Tp>::value;
> template <typename _Tp>
> - inline constexpr bool is_compound_v = is_compound<_Tp>::value;
> + inline constexpr bool is_compound_v = !is_fundamental_v<_Tp>;
> template <typename _Tp>
> inline constexpr bool is_member_pointer_v =
> is_member_pointer<_Tp>::value;
> template <typename _Tp>
> --
> 2.41.0
>
>
next prev parent reply other threads:[~2023-08-08 20:33 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 12:57 [PATCH 1/2] c++, libstdc++: implement __is_arithmetic built-in trait Ken Matsui
2023-07-09 12:57 ` [PATCH 2/2] libstdc++: use new built-in trait __is_arithmetic Ken Matsui
2023-07-09 13:03 ` [PATCH 1/2] c++, libstdc++: implement __is_arithmetic built-in trait Ken Matsui
2023-07-15 4:55 ` [PATCH v2 1/3] c++, libstdc++: Implement " Ken Matsui
2023-07-15 4:55 ` [PATCH v2 2/3] libstdc++: Optimize is_arithmetic performance by __is_arithmetic built-in Ken Matsui
2023-07-16 12:32 ` François Dumont
2023-07-17 4:48 ` Ken Matsui
2023-07-22 13:39 ` François Dumont
2023-08-08 20:09 ` Jonathan Wakely
2023-08-08 20:28 ` Jonathan Wakely
2023-07-15 4:55 ` [PATCH v2 3/3] libstdc++: Optimize is_fundamental " Ken Matsui
2023-07-15 5:07 ` Ken Matsui
2023-07-16 12:41 ` François Dumont
2023-07-17 4:49 ` Ken Matsui
2023-07-18 6:24 ` Ken Matsui
2023-07-18 6:26 ` Ken Matsui
2023-08-08 20:14 ` Jonathan Wakely
2023-08-31 13:47 ` Ken Matsui
2023-07-22 13:45 ` François Dumont
2023-08-08 20:18 ` Jonathan Wakely
2023-08-31 13:57 ` Ken Matsui
2023-08-31 15:01 ` Ken Matsui
2023-07-16 12:27 ` [PATCH v2 1/3] c++, libstdc++: Implement __is_arithmetic built-in trait François Dumont
2023-07-17 4:46 ` Ken Matsui
2023-07-18 6:27 ` [PATCH v3 " Ken Matsui
2023-07-18 6:27 ` [PATCH v3 2/3] libstdc++: Optimize is_arithmetic performance by __is_arithmetic built-in Ken Matsui
2023-07-18 6:27 ` [PATCH v3 3/3] libstdc++: Optimize is_fundamental " Ken Matsui
2023-07-18 7:40 ` [PATCH v4 1/4] c++, libstdc++: Implement __is_arithmetic built-in trait Ken Matsui
2023-07-18 7:40 ` [PATCH v4 2/4] libstdc++: Optimize is_arithmetic trait performance Ken Matsui
2023-07-18 7:40 ` [PATCH v4 3/4] libstdc++: Optimize is_fundamental " Ken Matsui
2023-07-18 7:40 ` [PATCH v4 4/4] libstdc++: Optimize is_compound " Ken Matsui
2023-08-08 20:33 ` Jonathan Wakely [this message]
2023-09-01 10:40 ` Ken Matsui
2023-07-22 13:50 ` [PATCH v3 1/3] c++, libstdc++: Implement __is_arithmetic built-in trait François Dumont
2023-08-08 20:04 ` Jonathan Wakely
2023-09-01 11:25 ` [PATCH v5 1/4] " Ken Matsui
2023-09-01 11:25 ` [PATCH v5 2/4] libstdc++: Optimize is_arithmetic trait performance Ken Matsui
2023-09-01 11:25 ` [PATCH v5 3/4] libstdc++: Optimize is_fundamental " Ken Matsui
2023-09-01 11:25 ` [PATCH v5 4/4] libstdc++: Optimize is_compound " Ken Matsui
2023-09-04 10:27 ` [PATCH v5 1/4] c++, libstdc++: Implement __is_arithmetic built-in trait Jonathan Wakely
2023-09-04 15:00 ` 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=CACb0b4n0JjbxrXFVexGcZ9s07LmcGCWzgRD5+QLRJDgtEvfAvw@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--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).