public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/98736] [10 Regression] Wrong partition order generated in loop distribution pass since r10-619-g5879ab5fafedc8f6
Date: Fri, 23 Apr 2021 13:00:38 +0000	[thread overview]
Message-ID: <bug-98736-4-75xW95xsQV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98736-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98736

--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:6c6a1173cccfd9c466e43bafa7ef7940b93d1495

commit r10-9758-g6c6a1173cccfd9c466e43bafa7ef7940b93d1495
Author: Bin Cheng <bin.cheng@linux.alibaba.com>
Date:   Wed Apr 7 10:24:32 2021 +0800

    tree-optimization/98736 - use programing order preserved RPO in ldist

    Tree loop distribution uses RPO to build reduced dependence graph,
    it's important that RPO preserves the original programing order.
    Though it usually does so, when distributing loop nest, exit BB can
    be placed before some loop BBs while after loop header.  This patch
    fixes the issue by calling rev_post_order_and_mark_dfs_back_seme.

    gcc/ChangeLog:

            PR tree-optimization/98736
            * tree-loop-distribution.c
            * (loop_distribution::bb_top_order_init):
            Compute RPO with programing order preserved by calling function
            rev_post_order_and_mark_dfs_back_seme.

    gcc/testsuite/ChangeLog:

            PR tree-optimization/98736
            * gcc.c-torture/execute/pr98736.c: New test.

    (cherry picked from commit e0bdccac582c01c928a05f26edcd8f5ac24669eb)

  parent reply	other threads:[~2021-04-23 13:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 19:40 [Bug tree-optimization/98736] New: Wrong partition order generated in loop distribution pass krebbel at gcc dot gnu.org
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 [this message]
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-75xW95xsQV@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).