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/107323] [10/11 Regression] Loop distribute issue
Date: Tue, 24 Jan 2023 15:22:51 +0000 [thread overview]
Message-ID: <bug-107323-4-Rdq5BPQIMT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107323-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107323
--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:28fe903730d2c6e424732184ab2d8b1e7d46db6c
commit r11-10482-g28fe903730d2c6e424732184ab2d8b1e7d46db6c
Author: Richard Biener <rguenther@suse.de>
Date: Fri Oct 21 09:45:44 2022 +0200
tree-optimization/107323 - loop distribution partition ordering issue
The following reverts part of the PR94125 fix which causes us to
use a bogus partition ordering after applying versioning for
alias to the testcase in PR107323. Instead PR94125 is fixed by
appropriately considering to be merged SCCs when skipping edges
we want to ignore because of the alias versioning.
PR tree-optimization/107323
* tree-loop-distribution.c (pg_unmark_merged_alias_ddrs):
New function.
(loop_distribution::break_alias_scc_partitions): Revert
postorder save/restore from the PR94125 fix. Instead
make sure to not ignore edges from SCCs we are going to
merge.
* gcc.dg/tree-ssa/pr107323.c: New testcase.
(cherry picked from commit 09f9814dc02c161ed78604c6df70b19b596f7524)
next prev parent reply other threads:[~2023-01-24 15:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 19:42 [Bug tree-optimization/107323] New: Problem with GCC optimizition fatemetmhr at gmail dot com
2022-10-19 19:59 ` [Bug tree-optimization/107323] [10/11/12 Regression] Loop distribute issue pinskia at gcc dot gnu.org
2022-10-20 9:09 ` marxin at gcc dot gnu.org
2022-10-20 9:12 ` marxin at gcc dot gnu.org
2022-10-20 9:21 ` rguenth at gcc dot gnu.org
2022-10-20 11:28 ` rguenth at gcc dot gnu.org
2022-10-20 11:36 ` rguenth at gcc dot gnu.org
2022-10-21 7:07 ` rguenth at gcc dot gnu.org
2022-10-21 7:35 ` rguenth at gcc dot gnu.org
2022-10-21 9:17 ` cvs-commit at gcc dot gnu.org
2022-10-21 9:19 ` cvs-commit at gcc dot gnu.org
2022-10-21 9:20 ` [Bug tree-optimization/107323] [10/11 " rguenth at gcc dot gnu.org
2023-01-10 8:00 ` rguenth at gcc dot gnu.org
2023-01-24 15:22 ` cvs-commit at gcc dot gnu.org [this message]
2023-01-26 13:05 ` [Bug tree-optimization/107323] [10 " cvs-commit at gcc dot gnu.org
2023-01-26 13:06 ` 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-107323-4-Rdq5BPQIMT@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).