public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/104931] [9/10/11 Regression] wrong-code with number_of_iterations_lt_to_ne Date: Thu, 17 Mar 2022 13:53:09 +0000 [thread overview] Message-ID: <bug-104931-4-xeOT5GZyR8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104931-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104931 --- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> --- Created attachment 52646 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52646&action=edit ivcanon dump from the GIMPLE testcase (without bug) The difference is that with LTO we have expanded expressions to Analyzing # of iterations of loop 1 exit condition [(struct TValue *) (_2 + 4294967272) + 12, + , 24](no_overflow) < _2 + 4294967272 while with the GIMPLE testcase we immediately get to Statement (exit)if (from_26 < to_27) is executed at most 0 (bounded by 0) + 1 times in loop 1. ... Loop 1 iterates 0 times. Note the GIMPLE FE doesn't yet support parsing CLOBBER stmts (but I'm quite sure this doesn't matter here) and for the loops() support you need to commit a pending patch.
next prev parent reply other threads:[~2022-03-17 13:53 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-15 10:20 [Bug tree-optimization/104931] New: " rguenth at gcc dot gnu.org 2022-03-15 10:20 ` [Bug tree-optimization/104931] " rguenth at gcc dot gnu.org 2022-03-15 10:37 ` rguenth at gcc dot gnu.org 2022-03-15 13:11 ` rguenth at gcc dot gnu.org 2022-03-16 12:34 ` rguenth at gcc dot gnu.org 2022-03-16 13:09 ` rguenth at gcc dot gnu.org 2022-03-16 13:14 ` [Bug tree-optimization/104931] [9/10/11 Regression] " rguenth at gcc dot gnu.org 2022-03-16 13:32 ` rguenth at gcc dot gnu.org 2022-03-17 13:45 ` rguenth at gcc dot gnu.org 2022-03-17 13:46 ` rguenth at gcc dot gnu.org 2022-03-17 13:53 ` rguenth at gcc dot gnu.org [this message] 2022-03-17 14:27 ` rguenth at gcc dot gnu.org 2022-03-23 14:08 ` cvs-commit at gcc dot gnu.org 2022-05-27 9:47 ` [Bug tree-optimization/104931] [10 " rguenth at gcc dot gnu.org 2022-06-28 10:48 ` jakub at gcc dot gnu.org 2023-07-07 9:58 ` rguenth 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-104931-4-xeOT5GZyR8@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).