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/112281] [12/13/14 Regression] wrong code at -O3 on x86_64-linux-gnu since r12-2097-g9f34b780b0461e
Date: Mon, 20 Nov 2023 14:01:52 +0000 [thread overview]
Message-ID: <bug-112281-4-5D2k8mcVBr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112281-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112281
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:3b34902417259031823bff7f853f615a60464bbd
commit r14-5626-g3b34902417259031823bff7f853f615a60464bbd
Author: Richard Biener <rguenther@suse.de>
Date: Mon Nov 20 13:39:52 2023 +0100
tree-optimization/112281 - loop distribution and zero dependence distances
The following fixes an omission in dependence testing for loop
distribution. When the overall dependence distance is not zero but
the dependence direction in the innermost common loop is = there is
a conflict between the partitions and we have to merge them.
PR tree-optimization/112281
* tree-loop-distribution.cc
(loop_distribution::pg_add_dependence_edges): For = in the
innermost common loop record a partition conflict.
* gcc.dg/torture/pr112281-1.c: New testcase.
* gcc.dg/torture/pr112281-2.c: Likewise.
next prev parent reply other threads:[~2023-11-20 14:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 20:51 [Bug tree-optimization/112281] New: wrong code at -O3 on x86_64-linux-gnu zhendong.su at inf dot ethz.ch
2023-10-29 21:07 ` [Bug tree-optimization/112281] [12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-10-29 21:20 ` pinskia at gcc dot gnu.org
2023-10-29 21:21 ` pinskia at gcc dot gnu.org
2023-10-30 7:04 ` sjames at gcc dot gnu.org
2023-10-30 8:57 ` [Bug tree-optimization/112281] [12/13/14 Regression] wrong code at -O3 on x86_64-linux-gnu since r12-2097-g9f34b780b0461e sjames at gcc dot gnu.org
2023-10-30 14:21 ` rguenth at gcc dot gnu.org
2023-11-14 10:38 ` rguenth at gcc dot gnu.org
2023-11-14 12:50 ` cvs-commit at gcc dot gnu.org
2023-11-14 12:54 ` [Bug tree-optimization/112281] [12/13 " rguenth at gcc dot gnu.org
2023-11-17 13:51 ` [Bug tree-optimization/112281] [12/13/14 " rguenth at gcc dot gnu.org
2023-11-17 13:53 ` rguenth at gcc dot gnu.org
2023-11-20 12:38 ` rguenth at gcc dot gnu.org
2023-11-20 14:01 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-20 14:02 ` [Bug tree-optimization/112281] [12/13 " rguenth at gcc dot gnu.org
2024-05-08 11:50 ` cvs-commit at gcc dot gnu.org
2024-05-17 11:12 ` [Bug tree-optimization/112281] [12 " cvs-commit at gcc dot gnu.org
2024-05-17 11:13 ` 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-112281-4-5D2k8mcVBr@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).