public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/98736] New: Wrong partition order generated in loop distribution pass
Date: Mon, 18 Jan 2021 19:40:45 +0000 [thread overview]
Message-ID: <bug-98736-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98736
Bug ID: 98736
Summary: Wrong partition order generated in loop distribution
pass
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: krebbel at gcc dot gnu.org
Target Milestone: ---
int a[6];
char b, c;
int main() {
int d[4] = {0, 0, 0, 0};
for (c = 0; c <= 5; c++) {
for (b = 2; b != 0; b++)
a[c] = 8;
a[c] = d[3];
}
if (a[0] != 0)
__builtin_abort();
}
Aborts when compiled with:
gcc -Os -march=z13 t.c -o t
Succeeds with:
gcc -O3 -march=z13 t.c -o t
The outer loop is recognized as clearmem. Unfortunately it is generated before
the inner loop body.
next reply other threads:[~2021-01-18 19:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 19:40 krebbel at gcc dot gnu.org [this message]
2021-01-18 19:41 ` [Bug tree-optimization/98736] " krebbel at gcc dot gnu.org
2021-01-19 7:52 ` [Bug tree-optimization/98736] [10/11 Regression] " rguenth at gcc dot gnu.org
2021-01-19 9:30 ` [Bug tree-optimization/98736] [10/11 Regression] Wrong partition order generated in loop distribution pass since r10-619-g5879ab5fafedc8f6 marxin at gcc dot gnu.org
2021-02-17 15:07 ` amker at gcc dot gnu.org
2021-03-21 4:41 ` amker at gcc dot gnu.org
2021-04-07 2:29 ` cvs-commit at gcc dot gnu.org
2021-04-07 2:32 ` amker at gcc dot gnu.org
2021-04-07 7:19 ` rguenth at gcc dot gnu.org
2021-04-07 7:21 ` [Bug tree-optimization/98736] [10 " rguenth at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-04-23 13:00 ` cvs-commit at gcc dot gnu.org
2021-04-23 13:01 ` 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-98736-4@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).