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: Tue, 21 Mar 2023 12:38:41 +0000	[thread overview]
Message-ID: <bug-109184-4-LQsqPCc1fu@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 #13 from Richard Biener <rguenth at gcc dot gnu.org> ---
Testcase with just the essential stuff.

static int g_1731[7] = { 42, 0, 0, 0, 0, 0, 42 };

void __attribute__((noipa)) foo ()
{
  int l_1930[5] = { 0, };

  for (int i = 0; i < 15; ++i)
    for (int j = 4; (j >= 1); j -= 1)
#pragma GCC unroll 0
      for (int k = 0; (k <= 4); k += 1)
        g_1731[(j + 1)] = --l_1930[k];
}

int main()
{
  foo ();
  if (g_1731[0] != 42
      || g_1731[1] != 0 || g_1731[2] != -60 || g_1731[3] != -59
      || g_1731[4] != -58 || g_1731[5] != -57
      || g_1731[6] != 42)
    __builtin_abort ();
  return 0;
}


The innermost loop body then is

  <bb 3> [local count: 894749066]:
  # k_26 = PHI <k_17(11), 0(5)>
  # ivtmp_23 = PHI <ivtmp_21(11), 5(5)>
  _1 = l_1930[k_26];
  _2 = _1 + -1;
  l_1930[k_26] = _2;
  g_1731[_6] = _2;
  k_17 = k_26 + 1;
  ivtmp_21 = ivtmp_23 - 1;
  if (ivtmp_21 != 0)

one should note that for data dependence analysis we'd usually need to
treat scalars (in this case SSA names) as arrays of the size of the
whole nest iteration domain and the dependences would be between
statements, not reads/writes.  So the above is

  _1 = l_1930[k_26];
  _2[i] = _1 + -1;
  l_1930[k_26] = _2[i];
  g_1731[_6] = _2[i];

then and when we interchange the loop we suddenly need two different
_2[] elements and when eliminating _2[] there's a dependence between
the l_1930 store and the implied load from a different iteration.

Note that when l_1930[k] wouldn't be stored to g_1731[j+1] the
interchange would be of course valid and we do not want to break
that case.

  parent reply	other threads:[~2023-03-21 12:38 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
2023-03-20 13:09 ` acoplan at gcc dot gnu.org
2023-03-21 12:38 ` rguenth at gcc dot gnu.org [this message]
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-LQsqPCc1fu@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).