public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/112312] -O3 produces worse code than -O2 for std::ranges::lower_bound in some cases, not marking a loop as finite Date: Tue, 20 Feb 2024 14:02:47 +0000 [thread overview] Message-ID: <bug-112312-4-5y3E7N9Bek@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112312-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112312 --- Comment #4 from Martin Jambor <jamborm at gcc dot gnu.org> --- It seems this has been fixed in current master (which is to become gcc 14). If my bisecting is correct, it has been fixed by r14-5628-g53ba8d669550d3 (Jan Hubicka: inter-procedural value range propagation). I guess it would be nice to add this testcase to the testsuite, so I'm keeping this bug opened (and on my TODO list).
prev parent reply other threads:[~2024-02-20 14:02 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-31 11:52 [Bug middle-end/112312] New: GCC fails to optimize a C++ algorithm with a function passed in as well as with a lambda ville.voutilainen at gmail dot com 2023-10-31 19:12 ` [Bug middle-end/112312] " pinskia at gcc dot gnu.org 2023-10-31 19:16 ` [Bug tree-optimization/112312] " pinskia at gcc dot gnu.org 2023-10-31 19:23 ` [Bug tree-optimization/112312] -O3 produces worse code than -O2 for std::ranges::lower_bound in some cases, not marking a loop as finite pinskia at gcc dot gnu.org 2024-02-20 14:02 ` jamborm at gcc dot gnu.org [this message]
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-112312-4-5y3E7N9Bek@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).