public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/62167] [4.8 Regression][tail-merge] dead type-unsafe load replaces type-safe load Date: Wed, 19 Nov 2014 10:51:00 -0000 [thread overview] Message-ID: <bug-62167-4-L0cVG2GBJh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-62167-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62167 --- Comment #4 from vries at gcc dot gnu.org --- Author: vries Date: Wed Nov 19 10:50:42 2014 New Revision: 217763 URL: https://gcc.gnu.org/viewcvs?rev=217763&root=gcc&view=rev Log: Fix tail-merge pass for dead type-unsafe code 2014-11-19 Tom de Vries <tom@codesourcery.com> Backport from mainline PR tree-optimization/62167 * tree-ssa-tail-merge.c (stmt_local_def): Handle statements with vuse conservatively. (gimple_equal_p): Don't use vn_valueize to compare for lhs equality of assigns. * gcc.dg/pr51879-12.c: Add xfails. * gcc.dg/pr62167-run.c: New test. * gcc.dg/pr62167.c: New test. Added: branches/gcc-4_9-branch/gcc/testsuite/gcc.dg/pr62167-run.c branches/gcc-4_9-branch/gcc/testsuite/gcc.dg/pr62167.c Modified: branches/gcc-4_9-branch/gcc/ChangeLog branches/gcc-4_9-branch/gcc/testsuite/ChangeLog branches/gcc-4_9-branch/gcc/testsuite/gcc.dg/pr51879-12.c branches/gcc-4_9-branch/gcc/tree-ssa-tail-merge.c
next prev parent reply other threads:[~2014-11-19 10:51 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-18 8:47 [Bug tree-optimization/62167] New: [tail-merge] " vries at gcc dot gnu.org 2014-08-19 10:17 ` [Bug tree-optimization/62167] " vries at gcc dot gnu.org 2014-08-19 10:18 ` vries at gcc dot gnu.org 2014-11-18 17:08 ` [Bug tree-optimization/62167] [4.8 Regression][tail-merge] " vries at gcc dot gnu.org 2014-11-19 10:45 ` vries at gcc dot gnu.org 2014-11-19 10:51 ` vries at gcc dot gnu.org [this message] 2014-11-19 11:08 ` vries at gcc dot gnu.org 2014-11-19 11:22 ` vries 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-62167-4-L0cVG2GBJh@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).