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/95049] [9/10 Regression] GCC never terminates with trivial input program
Date: Tue, 23 Jun 2020 11:06:26 +0000 [thread overview]
Message-ID: <bug-95049-4-l1CgMZjhW5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95049-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95049
--- Comment #3 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:80416aac46779533476425424e06753bac67e148
commit r10-8348-g80416aac46779533476425424e06753bac67e148
Author: Richard Biener <rguenther@suse.de>
Date: Mon May 11 13:40:37 2020 +0200
tree-optimization/95049 - fix not terminating RPO VN iteration
This rejects lattice changes from one constant to another.
2020-05-11 Richard Biener <rguenther@suse.de>
PR tree-optimization/95049
* tree-ssa-sccvn.c (set_ssa_val_to): Reject lattice transition
between different constants.
* gcc.dg/torture/pr95049.c: New testcase.
next prev parent reply other threads:[~2020-06-23 11:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 9:00 [Bug c/95049] New: " luis at luismarques dot eu
2020-05-11 9:36 ` [Bug tree-optimization/95049] " rguenth at gcc dot gnu.org
2020-05-11 11:44 ` [Bug tree-optimization/95049] [9/10/11 Regression] " rguenth at gcc dot gnu.org
2020-05-11 15:53 ` cvs-commit at gcc dot gnu.org
2020-06-23 11:06 ` cvs-commit at gcc dot gnu.org [this message]
2020-09-11 10:38 ` [Bug tree-optimization/95049] [9 " cvs-commit at gcc dot gnu.org
2020-09-11 10:39 ` 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-95049-4-l1CgMZjhW5@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).