public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/60183] [4.7 Regression] phiprop creates invalid code Date: Mon, 17 Mar 2014 14:39:00 -0000 [thread overview] Message-ID: <bug-60183-4-z8tXkHUagi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60183-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60183 --- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> --- Author: rguenth Date: Mon Mar 17 14:38:55 2014 New Revision: 208618 URL: http://gcc.gnu.org/viewcvs?rev=208618&root=gcc&view=rev Log: 2014-03-17 Richard Biener <rguenther@suse.de> Backport from mainline 2013-05-21 Richard Biener <rguenther@suse.de> PR tree-optimization/57303 * tree-ssa-sink.c (statement_sink_location): Properly handle self-assignments. * gcc.dg/torture/pr57303.c: New testcase. 2013-12-02 Richard Biener <rguenther@suse.de> PR tree-optimization/59139 * tree-ssa-loop-niter.c (chain_of_csts_start): Properly match code in get_val_for. (get_val_for): Use gcc_checking_asserts. * gcc.dg/torture/pr59139.c: New testcase. 2014-02-14 Richard Biener <rguenther@suse.de> PR tree-optimization/60183 * tree-ssa-phiprop.c (propagate_with_phi): Avoid speculating loads. (tree_ssa_phiprop): Calculate and free post-dominators. * gcc.dg/torture/pr60183.c: New testcase. Added: branches/gcc-4_7-branch/gcc/testsuite/gcc.dg/torture/pr57303.c branches/gcc-4_7-branch/gcc/testsuite/gcc.dg/torture/pr59139.c branches/gcc-4_7-branch/gcc/testsuite/gcc.dg/torture/pr60183.c Modified: branches/gcc-4_7-branch/gcc/ChangeLog branches/gcc-4_7-branch/gcc/testsuite/ChangeLog branches/gcc-4_7-branch/gcc/tree-ssa-loop-niter.c branches/gcc-4_7-branch/gcc/tree-ssa-phiprop.c branches/gcc-4_7-branch/gcc/tree-ssa-sink.c
next prev parent reply other threads:[~2014-03-17 14:39 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-60183-4@http.gcc.gnu.org/bugzilla/> 2014-02-13 19:22 ` [Bug tree-optimization/60183] [4.7/4.8/4.9 " jakub at gcc dot gnu.org 2014-02-14 9:18 ` rguenth at gcc dot gnu.org 2014-02-14 9:22 ` jakub at gcc dot gnu.org 2014-02-14 9:28 ` rguenth at gcc dot gnu.org 2014-02-14 12:58 ` rguenth at gcc dot gnu.org 2014-02-15 9:55 ` rguenth at gcc dot gnu.org 2014-02-25 10:47 ` [Bug tree-optimization/60183] [4.7/4.8 " rguenth at gcc dot gnu.org 2014-02-25 10:48 ` [Bug tree-optimization/60183] [4.7 " rguenth at gcc dot gnu.org 2014-03-17 14:39 ` rguenth at gcc dot gnu.org [this message] 2014-03-17 14:40 ` 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-60183-4-z8tXkHUagi@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: linkBe 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).