From: "François Dumont" <frs.dumont@gmail.com>
To: Ken Matsui <kmatsui@cs.washington.edu>
Cc: Ken Matsui <kmatsui@gcc.gnu.org>,
gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH v2 2/3] libstdc++: Optimize is_arithmetic performance by __is_arithmetic built-in
Date: Sat, 22 Jul 2023 15:39:07 +0200 [thread overview]
Message-ID: <607569d3-9720-b28c-57cd-d7ca6cd0966d@gmail.com> (raw)
In-Reply-To: <CAML+3pW_ok-uepn8tvO+zDvpMOYdWyve4QA-1xB_3Nrn5VSZcQ@mail.gmail.com>
On 17/07/2023 06:48, Ken Matsui wrote:
> On Sun, Jul 16, 2023 at 5:32 AM François Dumont <frs.dumont@gmail.com> wrote:
>>
>> On 15/07/2023 06:55, Ken Matsui via Libstdc++ wrote:
>>> This patch optimizes the performance of the is_arithmetic trait by
>>> dispatching to the new __is_arithmetic built-in trait.
>>>
>>> libstdc++-v3/ChangeLog:
>>>
>>> * include/std/type_traits (is_arithmetic): Use __is_arithmetic
>>> built-in trait.
>>> (is_arithmetic_v): Likewise.
>>>
>>> Signed-off-by: Ken Matsui <kmatsui@gcc.gnu.org>
>>> ---
>>> libstdc++-v3/include/std/type_traits | 14 ++++++++++++++
>>> 1 file changed, 14 insertions(+)
>>>
>>> diff --git a/libstdc++-v3/include/std/type_traits b/libstdc++-v3/include/std/type_traits
>>> index 0e7a9c9c7f3..7ebbe04c77b 100644
>>> --- a/libstdc++-v3/include/std/type_traits
>>> +++ b/libstdc++-v3/include/std/type_traits
>>> @@ -655,10 +655,17 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
>>> { };
>>>
>>> /// is_arithmetic
>>> +#if __has_builtin(__is_arithmetic)
>>> + template<typename _Tp>
>>> + struct is_arithmetic
>>> + : public __bool_constant<__is_arithmetic(_Tp)>
>>> + { };
>>> +#else
>>> template<typename _Tp>
>>> struct is_arithmetic
>>> : public __or_<is_integral<_Tp>, is_floating_point<_Tp>>::type
>>> { };
>>> +#endif
>>>
>>> /// is_fundamental
>>> template<typename _Tp>
>>> @@ -3198,8 +3205,15 @@ template <typename _Tp>
>>> inline constexpr bool is_reference_v<_Tp&> = true;
>>> template <typename _Tp>
>>> inline constexpr bool is_reference_v<_Tp&&> = true;
>>> +
>>> +#if __has_builtin(__is_arithmetic)
>>> +template <typename _Tp>
>>> + inline constexpr bool is_arithmetic_v = __is_arithmetic(_Tp);
>>> +#else
>>> template <typename _Tp>
>>> inline constexpr bool is_arithmetic_v = is_arithmetic<_Tp>::value;
>>> +#endif
>>> +
>>> template <typename _Tp>
>>> inline constexpr bool is_fundamental_v = is_fundamental<_Tp>::value;
>>> template <typename _Tp>
>> Same remark as the one I did for __is_pointer in cpp_type_traits.h. You
>> could implement it as:
>>
>> template<typename _Tp>
>> struct __is_arithmetic_t
>> : public __truth_type<__is_arithmetic(_Tp)>
>> { };
>>
>> François
>>
> Thank you for your review! This is from the type_traits header, so the
> name should be as-is.
Here I meant that current libstdc++ implementation of
std::__is_arithmetic in cpp_type_traits.h should also make use of the
builtin __is_arithmetic that you are introducing. That is to say replace
this:
template<typename _Tp>
struct __is_arithmetic
: public __traitor<__is_integer<_Tp>, __is_floating<_Tp> >
{ };
by:
#if __has_builtin(__is_arithmetic)
template<typename _Tp>
struct __is_arithmetic_t
: public __truth_type<__is_arithmetic<_Tp>>
{ };
#else
template<typename _Tp>
struct __is_arithmetic_t
: public __traitor<__is_integer<_Tp>, __is_floating<_Tp> >
{ };
#endif
if you replace '__is_arithmetic' by '__is_arithmetic_t' for the
libstdc++, just adapt to the name you eventually adopt.
next prev parent reply other threads:[~2023-07-22 13:39 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 [this message]
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
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=607569d3-9720-b28c-57cd-d7ca6cd0966d@gmail.com \
--to=frs.dumont@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kmatsui@cs.washington.edu \
--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).