public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/107367] All standard library algorithms should optimize to pointers internally when they are contiguous iterators after C++20
Date: Tue, 25 Oct 2022 03:36:22 +0000 [thread overview]
Message-ID: <bug-107367-4-sdvTpqOcXL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107367-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107367
--- Comment #2 from cqwrteur <unlvsur at live dot com> ---
(In reply to cqwrteur from comment #1)
> This optimization will prevent duplications of templates over iterators and
> pointers. (vector<int>::iterator and int* duplications for example)
>
> For example:
>
> https://godbolt.org/z/9zEajxxa8
> vs
> https://godbolt.org/z/n61vEddj1
>
> 579 vs 879
For debugging. You can do something like this
template<typename ForwardIterator>
concept can_optimize_to_pointer_impl =
#ifdef _GLIBCXX_DEBUG
false;
#else
std::contiguous_iterator<ForwardIterator>&&!std::is_pointer_v<ForwardIterator>;
#endif
template<typename ForwardIterator>
constexpr void my_sort(ForwardIterator first,ForwardIterator last)
{
if constexpr(can_optimize_to_pointer_impl<ForwardIterator>)
{
std::sort(std::to_address(first),std::to_address(last));
}
else
{
std::sort(first,last);
}
}
https://godbolt.org/z/jj38MoWen
next prev parent reply other threads:[~2022-10-25 3:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 2:28 [Bug libstdc++/107367] New: All standard library algorithms should detect whether " unlvsur at live dot com
2022-10-24 2:33 ` [Bug libstdc++/107367] All standard library algorithms should optimize to pointers internally when " unlvsur at live dot com
2022-10-25 3:36 ` unlvsur at live dot com [this message]
2023-12-16 18:40 ` unlvsur at live dot com
2023-12-17 13:44 ` redi at gcc dot gnu.org
2023-12-17 13:45 ` redi at gcc dot gnu.org
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=bug-107367-4-sdvTpqOcXL@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).