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 r14-6624] libstdc++: Optimize std::is_bounded_array compilation performance Date: Sat, 16 Dec 2023 17:00:14 +0000 (GMT) [thread overview] Message-ID: <20231216170014.62A29386D63A@sourceware.org> (raw) https://gcc.gnu.org/g:8843cff6c98cb0789a1ec6f51be6c5122fc1b5e9 commit r14-6624-g8843cff6c98cb0789a1ec6f51be6c5122fc1b5e9 Author: Ken Matsui <kmatsui@gcc.gnu.org> Date: Mon Sep 11 19:15:21 2023 -0700 libstdc++: Optimize std::is_bounded_array compilation performance This patch optimizes the compilation performance of std::is_bounded_array by dispatching to the new __is_bounded_array built-in trait. libstdc++-v3/ChangeLog: * include/std/type_traits (is_bounded_array_v): Use __is_bounded_array built-in trait. Signed-off-by: Ken Matsui <kmatsui@gcc.gnu.org> Reviewed-by: Jonathan Wakely <jwakely@redhat.com> Diff: --- libstdc++-v3/include/std/type_traits | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/libstdc++-v3/include/std/type_traits b/libstdc++-v3/include/std/type_traits index 64f9d67fe29..2a1a0aa80ff 100644 --- a/libstdc++-v3/include/std/type_traits +++ b/libstdc++-v3/include/std/type_traits @@ -3506,11 +3506,16 @@ template<typename _Ret, typename _Fn, typename... _Args> /// True for a type that is an array of known bound. /// @ingroup variable_templates /// @since C++20 +# if _GLIBCXX_USE_BUILTIN_TRAIT(__is_bounded_array) + template<typename _Tp> + inline constexpr bool is_bounded_array_v = __is_bounded_array(_Tp); +# else template<typename _Tp> inline constexpr bool is_bounded_array_v = false; template<typename _Tp, size_t _Size> inline constexpr bool is_bounded_array_v<_Tp[_Size]> = true; +# endif /// True for a type that is an array of unknown bound. /// @ingroup variable_templates
reply other threads:[~2023-12-16 17:00 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=20231216170014.62A29386D63A@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: linkBe 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).