public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/47679] [4.9/5/6 Regression] Strange uninitialized warning after SRA Date: Sun, 20 Sep 2015 06:40:00 -0000 [thread overview] Message-ID: <bug-47679-4-LQJLbQ7KMY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47679-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47679 --- Comment #31 from Jeffrey A. Law <law at gcc dot gnu.org> --- Author: law Date: Sun Sep 20 06:37:39 2015 New Revision: 227942 URL: https://gcc.gnu.org/viewcvs?rev=227942&root=gcc&view=rev Log: [PATCH] Fix 47679 by improving jump threading PR tree-optimization/47679 * tree-ssa-dom.c (record_temporary_equivalences): No longer static. * tree-ssa-dom.h (record_temporary_equivalences): Add prototype. * tree-ssa-threadedge.c: Include tree-ssa-dom.h. (thread_through_normal_block): Use record_temporary_equivalences. PR tree-optimization/47679 * g++.dg/warn/Wuninitialized-6.C: New test. Added: trunk/gcc/testsuite/g++.dg/warn/Wuninitialized-6.C Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-ssa-dom.c trunk/gcc/tree-ssa-dom.h trunk/gcc/tree-ssa-threadedge.c
prev parent reply other threads:[~2015-09-20 6:40 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-10 14:48 [Bug tree-optimization/47679] New: [4.6 " jakub at gcc dot gnu.org 2011-02-10 14:53 ` [Bug tree-optimization/47679] " jakub at gcc dot gnu.org 2011-02-10 16:00 ` jakub at gcc dot gnu.org 2011-02-10 16:19 ` rguenth at gcc dot gnu.org 2011-02-10 16:29 ` jakub at gcc dot gnu.org 2011-02-10 16:29 ` jakub at gcc dot gnu.org 2011-03-03 11:27 ` rguenth at gcc dot gnu.org 2011-03-25 20:09 ` [Bug tree-optimization/47679] [4.6/4.7 " jakub at gcc dot gnu.org 2011-06-27 16:00 ` jakub at gcc dot gnu.org 2011-10-26 17:57 ` jakub at gcc dot gnu.org 2012-03-01 15:16 ` jakub at gcc dot gnu.org 2013-04-12 15:16 ` [Bug tree-optimization/47679] [4.7/4.8/4.9 " jakub at gcc dot gnu.org 2013-08-30 13:04 ` Woebbeking at web dot de 2014-02-16 13:13 ` jackie.rosen at hushmail dot com 2014-06-12 13:44 ` [Bug tree-optimization/47679] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-12-19 13:27 ` [Bug tree-optimization/47679] [4.8/4.9/5 " jakub at gcc dot gnu.org 2015-01-12 17:11 ` gafnium@yandex-team.ru 2015-02-16 23:39 ` law at redhat dot com 2015-04-15 18:52 ` [Bug tree-optimization/47679] [4.8/4.9/5/6 " law at gcc dot gnu.org 2015-04-17 19:24 ` law at gcc dot gnu.org 2015-06-23 8:23 ` rguenth at gcc dot gnu.org 2015-06-26 19:56 ` [Bug tree-optimization/47679] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:28 ` jakub at gcc dot gnu.org 2015-09-14 20:11 ` law at gcc dot gnu.org 2015-09-15 17:04 ` law at gcc dot gnu.org 2015-09-16 17:26 ` law at gcc dot gnu.org 2015-09-17 3:01 ` law at gcc dot gnu.org 2015-09-18 15:29 ` law at gcc dot gnu.org 2015-09-18 19:34 ` law at gcc dot gnu.org 2015-09-19 2:57 ` law at gcc dot gnu.org 2015-09-20 6:16 ` law at redhat dot com 2015-09-20 6:40 ` [Bug tree-optimization/47679] [4.9/5 " law at redhat dot com 2015-09-20 6:40 ` law at gcc dot gnu.org [this message]
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-47679-4-LQJLbQ7KMY@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).