public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107114] [13 Regression] Failure to discover range results in bogus warning Date: Mon, 03 Oct 2022 18:18:17 +0000 [thread overview] Message-ID: <bug-107114-4-3IF79aHHPA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107114-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107114 --- Comment #3 from Andrew Macleod <amacleod at redhat dot com> --- yeah, we just invoke the loop analyzer and pick up what it tells us. From VRP2 point of view, it is just not getting the info supplied from the loop optimizer. I see dom3 removes some code and I see < fix_loop_structure: removing loop 5 any chance it doesn't fix it up right somehow?
next prev parent reply other threads:[~2022-10-03 18:18 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-01 17:59 [Bug tree-optimization/107114] New: " jeffreyalaw at gmail dot com 2022-10-01 18:01 ` [Bug tree-optimization/107114] " law at gcc dot gnu.org 2022-10-03 15:46 ` amacleod at redhat dot com 2022-10-03 17:37 ` law at gcc dot gnu.org 2022-10-03 18:18 ` amacleod at redhat dot com [this message] 2022-10-03 18:21 ` law at gcc dot gnu.org 2022-10-06 9:27 ` rguenth at gcc dot gnu.org 2022-12-22 14:32 ` rguenth at gcc dot gnu.org 2023-02-21 13:51 ` 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-107114-4-3IF79aHHPA@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).