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/101145] niter analysis fails for until-wrap condition
Date: Mon, 21 Jun 2021 09:02:30 +0000 [thread overview]
Message-ID: <bug-101145-4-NkZLH7o53k@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101145-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101145
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Last reconfirmed| |2021-06-21
Keywords| |missed-optimization
CC| |amker at gcc dot gnu.org,
| |guojiufu at gcc dot gnu.org
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
This comes up with a pending patch to split loops like
void
foo (int *a, int *b, unsigned l, unsigned n)
{
while (++l != n)
a[l] = b[l] + 1;
}
into
while (++l > n)
a[l] = b[l] + 1;
while (++l < n)
a[l] = b[l] + 1;
since for the second loop (the "usual" case involving no wrapping of the IV)
this results in affine IVs and thus analyzable data dependence.
next prev parent reply other threads:[~2021-06-21 9:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 8:59 [Bug tree-optimization/101145] New: " rguenth at gcc dot gnu.org
2021-06-21 9:02 ` rguenth at gcc dot gnu.org [this message]
2021-06-24 15:39 ` [Bug tree-optimization/101145] " amker at gcc dot gnu.org
2021-06-25 1:28 ` guojiufu at gcc dot gnu.org
2021-06-25 1:34 ` amker at gcc dot gnu.org
2021-06-25 10:13 ` guojiufu at gcc dot gnu.org
2021-06-25 12:24 ` guojiufu at gcc dot gnu.org
2021-06-26 2:53 ` amker at gcc dot gnu.org
2021-07-01 3:42 ` guojiufu at gcc dot gnu.org
2021-08-25 8:39 ` cvs-commit at gcc dot gnu.org
2021-08-31 13:27 ` cvs-commit at gcc dot gnu.org
2021-09-17 10:01 ` marxin at gcc dot gnu.org
2021-12-01 19:59 ` cvs-commit 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-101145-4-NkZLH7o53k@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).