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] New: All standard library algorithms should detect whether they are contiguous iterators after C++20 Date: Mon, 24 Oct 2022 02:28:12 +0000 [thread overview] Message-ID: <bug-107367-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107367 Bug ID: 107367 Summary: All standard library algorithms should detect whether they are contiguous iterators after C++20 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: unlvsur at live dot com Target Milestone: --- https://github.com/gcc-mirror/gcc/blob/00716b776200c2de6813ce706d2757eec4cb2735/libstdc%2B%2B-v3/include/bits/stl_algo.h#L3229 Take is_sorted for example: template<typename _ForwardIterator> _GLIBCXX20_CONSTEXPR inline bool is_sorted(_ForwardIterator __first, _ForwardIterator __last) { return std::is_sorted_until(__first, __last) == __last; } It should be optimized to template<typename _ForwardIterator> _GLIBCXX20_CONSTEXPR inline bool is_sorted(_ForwardIterator __first, _ForwardIterator __last) { if constexpr(contiguous_iterator<_ForwardIterator>&&!is_pointer_v<_ForwardIterator>) { return is_sorted(to_address(__first),to_address(__last)); } else { return std::is_sorted_until(__first, __last) == __last; } }
next reply other threads:[~2022-10-24 2:28 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-24 2:28 unlvsur at live dot com [this message] 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 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@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: 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).