public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/101653] [9/10/11/12 Regression] Bad code generated when optimizing nested for loops
Date: Tue, 27 Jul 2021 23:13:49 +0000 [thread overview]
Message-ID: <bug-101653-4-8TUrEF1f5W@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101653-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101653
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
So the loop of PR 100740 is same as this one so marking as a dup.
That is both have a double loop and the inner one has loop exit which is bound
by comparing of the induction variable that is counting how many times inside
the loop it has happened and comparing it against in the inner loop induction
variable.
*** This bug has been marked as a duplicate of bug 100740 ***
prev parent reply other threads:[~2021-07-27 23:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 22:48 [Bug c/101653] New: " phd at phd dot re
2021-07-27 22:55 ` [Bug tree-optimization/101653] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org
2021-07-27 23:01 ` jakub at gcc dot gnu.org
2021-07-27 23:09 ` pinskia at gcc dot gnu.org
2021-07-27 23:13 ` pinskia 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-101653-4-8TUrEF1f5W@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).