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] [11/12/13/14 Regression] csmith: 2017 bug with -floop-interchange
Date: Tue, 14 Nov 2023 12:44:56 +0000	[thread overview]
Message-ID: <bug-109184-4-E1pfNkRtIS@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 #15 from Richard Biener <rguenth at gcc dot gnu.org> ---
Note even when promoting _2 to an array there wouldn't be any data dependence
between the actual refs.  There's a dependence between stmts, but that doesn't
exactly capture the issue either.  Consider

int a[1024], b[1024];

void foo()
{    
  for (int i = 0; i < 32; ++i)
    for (int j = 0; j < 32; ++j)
      for (int k = 0; k < 32; ++k)
        a[j] = b[k];
} 

where interchange of the two outer loops would be valid since b[k] doesn't
change.  Likewise

  for (int i = 0; i < 32; ++i)
    for (int j = 0; j < 32; ++j)
      for (int k = 0; k < 32; ++k)
        {
          b[k] = b[k] + 1;
          a[j] = 0;
        }

would be valid to interchange.  For the testcase at hand
tree_loop_interchange::valid_data_dependences only gets the l_1930[] update
as data-dependence that's not statically resolved.

If we'd have that ominous _2[i] and

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

we'd only have extra zero-distance DDRs here and we ignore those.

      parent reply	other threads:[~2023-11-14 12:44 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
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 [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-109184-4-E1pfNkRtIS@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).