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/109184] [10/11/12/13 Regression] csmith: 2017 bug with -floop-interchange
Date: Mon, 20 Mar 2023 13:00:41 +0000 [thread overview]
Message-ID: <bug-109184-4-ZIW6d5F724@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109184-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109184
--- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fails even with -O2 -floop-interchange -fno-move-loop-stores (otherwise we
complicate the IL by applying store-motion to g_1731).
(compute_affine_dependence
ref_a: l_1930[k_33], stmt_a: _1 = l_1930[k_33];
ref_b: g_1731[_51], stmt_b: g_1731[_51] = _5;
) -> no dependence
(compute_affine_dependence
ref_a: l_1930[k_33], stmt_a: l_1930[k_33] = _2;
ref_b: g_1731[_51], stmt_b: _4 = g_1731[_51];
) -> no dependence
(compute_affine_dependence
ref_a: l_1930[k_33], stmt_a: l_1930[k_33] = _2;
ref_b: g_1731[_51], stmt_b: g_1731[_51] = _5;
) -> no dependence
maybe I'm missing something but we seem to fail to honor dependences from
SSA edges?
<bb 3> [local count: 894749066]:
# k_33 = PHI <k_24(11), 0(5)>
# ivtmp_41 = PHI <ivtmp_40(11), 5(5)>
_1 = l_1930[k_33];
_2 = _1 + 18446744073709551615;
l_1930[k_33] = _2;
_4 = g_1731[_51];
_38 = _2 & _4;
_5 = _38 & 38;
g_1731[_51] = _5;
k_24 = k_33 + 1;
ivtmp_40 = ivtmp_41 - 1;
if (ivtmp_40 != 0)
Of course DDR_ARE_DEPENDENT (ddr) == chrec_known just tells us there's no
memory dependece.
As said, maybe I'm missing something ...
next prev parent reply other threads:[~2023-03-20 13:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 11:21 [Bug c/109184] New: csmith: really old bug with -O3 dcb314 at hotmail dot com
2023-03-18 11:33 ` [Bug c/109184] " dcb314 at hotmail dot com
2023-03-18 12:27 ` dcb314 at hotmail dot com
2023-03-18 12:42 ` dcb314 at hotmail dot com
2023-03-18 15:49 ` [Bug tree-optimization/109184] [10/11/12/13 Regression] " jakub at gcc dot gnu.org
2023-03-20 9:20 ` [Bug tree-optimization/109184] [10/11/12/13 Regression] csmith: 2017 bug with -floop-interchange rguenth at gcc dot gnu.org
2023-03-20 10:34 ` rguenth at gcc dot gnu.org
2023-03-20 10:58 ` rguenth at gcc dot gnu.org
2023-03-20 12:39 ` rguenth at gcc dot gnu.org
2023-03-20 12:46 ` jakub at gcc dot gnu.org
2023-03-20 12:50 ` rguenth at gcc dot gnu.org
2023-03-20 13:00 ` rguenth at gcc dot gnu.org [this message]
2023-03-20 13:09 ` acoplan at gcc dot gnu.org
2023-03-21 12:38 ` rguenth at gcc dot gnu.org
2023-03-27 7:31 ` rguenth at gcc dot gnu.org
2023-07-07 10:45 ` [Bug tree-optimization/109184] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-11-14 12:44 ` 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-109184-4-ZIW6d5F724@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).