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/105276] [12 Regression] executed once loop not optimized anymore
Date: Thu, 21 Apr 2022 15:46:27 +0000 [thread overview]
Message-ID: <bug-105276-4-F7rNns8gRO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105276-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105276
--- Comment #3 from Andrew Macleod <amacleod at redhat dot com> ---
Created attachment 52848
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52848&action=edit
proposed patch
When I removed the recursion from range_of_stmt, I neglected to incorporate the
existing known global range for an ssa-name into the calculated value.
Range_of_stmt does this, but the prefill calculation missed it. This patch
fixes that oversight.
next prev parent reply other threads:[~2022-04-21 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 13:47 [Bug c/105276] New: " denis.campredon at gmail dot com
2022-04-19 8:29 ` [Bug tree-optimization/105276] " rguenth at gcc dot gnu.org
2022-04-20 15:38 ` jakub at gcc dot gnu.org
2022-04-21 15:46 ` amacleod at redhat dot com [this message]
2022-04-25 13:59 ` cvs-commit at gcc dot gnu.org
2022-04-25 14:27 ` amacleod at redhat dot com
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-105276-4-F7rNns8gRO@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: link
Be 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).