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/100934] [9/10 Regression] wrong code at -O3 during unrolling since r9-6299
Date: Wed, 16 Jun 2021 14:24:31 +0000 [thread overview]
Message-ID: <bug-100934-4-IYEjgYdEgL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100934-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100934
--- Comment #14 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:b7878d4e179c72ad69cdd103fbbfe16bc38010db
commit r10-9924-gb7878d4e179c72ad69cdd103fbbfe16bc38010db
Author: Richard Biener <rguenther@suse.de>
Date: Mon Jun 14 14:57:26 2021 +0200
tree-optimization/100934 - properly mark irreducible regions for DOM
The jump threading code requires marked irreducible regions for the
purpose of validating jump threading paths but DOM fails to provide
that resulting in mised number of iteration upper bounds clearing.
2021-06-14 Richard Biener <rguenther@suse.de>
PR tree-optimization/100934
* tree-ssa-dom.c (pass_dominator::execute): Properly
mark irreducible regions.
* gcc.dg/torture/pr100934.c: New testcase.
(cherry picked from commit 788bb7edb3975b80c4cb16323e7a5e55a2471e46)
next prev parent reply other threads:[~2021-06-16 14:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 20:49 [Bug tree-optimization/100934] New: wrong code at -O3 on x86_64-linux-gnu zhendong.su at inf dot ethz.ch
2021-06-06 21:07 ` [Bug tree-optimization/100934] [9/10/11/12 Regression] wrong code at -O3 during unrolling pinskia at gcc dot gnu.org
2021-06-07 8:38 ` [Bug tree-optimization/100934] [9/10/11/12 Regression] wrong code at -O3 during unrolling since r9-6299 jakub at gcc dot gnu.org
2021-06-07 8:42 ` jakub at gcc dot gnu.org
2021-06-07 10:28 ` rguenth at gcc dot gnu.org
2021-06-07 13:13 ` rguenth at gcc dot gnu.org
2021-06-11 9:28 ` rguenth at gcc dot gnu.org
2021-06-14 2:48 ` law at gcc dot gnu.org
2021-06-14 12:56 ` rguenth at gcc dot gnu.org
2021-06-14 12:59 ` jakub at gcc dot gnu.org
2021-06-14 13:02 ` rguenther at suse dot de
2021-06-14 14:37 ` cvs-commit at gcc dot gnu.org
2021-06-14 14:39 ` [Bug tree-optimization/100934] [9/10/11 " rguenth at gcc dot gnu.org
2021-06-16 13:12 ` cvs-commit at gcc dot gnu.org
2021-06-16 14:24 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-13 10:09 ` [Bug tree-optimization/100934] [9 " cvs-commit at gcc dot gnu.org
2021-10-13 10:10 ` rguenth at gcc dot gnu.org
2021-11-09 7:57 ` pinskia 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-100934-4-IYEjgYdEgL@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).