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 tree-optimization/107502] New: GCC fails to detect foo(first_const,last)-first_const+first pattern Date: Tue, 01 Nov 2022 19:34:13 +0000 [thread overview] Message-ID: <bug-107502-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107502 Bug ID: 107502 Summary: GCC fails to detect foo(first_const,last)-first_const+first pattern Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: unlvsur at live dot com Target Milestone: --- GCC fails to detect foo(first_const,last)-first_const+first pattern. This is to use C++ std::contiguous_iterator interfaces with char const* foo(char const* first, char const* last) noexcept; like APIs. However, GCC fails to detect they are the same in IR and make them tail calls. See godbolt: https://godbolt.org/z/67PvYPar8
next reply other threads:[~2022-11-01 19:34 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-01 19:34 unlvsur at live dot com [this message] 2022-11-01 19:43 ` [Bug tree-optimization/107502] " pinskia at gcc dot gnu.org 2022-11-01 19:46 ` pinskia at gcc dot gnu.org 2022-11-01 19:51 ` pinskia at gcc dot gnu.org 2022-11-01 22:50 ` unlvsur at live dot com 2022-11-01 22:56 ` pinskia 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-107502-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).