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/67816] [6 Regression] ICE in duplicate_thread_path, 186.crafty fails to build Date: Wed, 07 Oct 2015 02:26:00 -0000 [thread overview] Message-ID: <bug-67816-4-ZYULG78wOy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67816-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67816 --- Comment #13 from Jeffrey A. Law <law at gcc dot gnu.org> --- Author: law Date: Wed Oct 7 02:25:57 2015 New Revision: 228559 URL: https://gcc.gnu.org/viewcvs?rev=228559&root=gcc&view=rev Log: [PATCH][PR tree-optimization/67816] Fix jump threading when DOM removes conditionals in jump threading path PR tree-optimization/67816 * tree-ssa-threadupdate.h (remove_jump_threads_including): Renamed from remove_jump_threads_starting_at. Accept an edge rather than a basic block. * tree-ssa-threadupdate.c (removed_edges): New hash table. (remove_jump_threads_including): Note edges that get removed from the CFG for later pruning of jump threading paths including them. (thread_through_all_blocks): Remove paths which include edges that have been removed. * tree-ssa-dom.c (optimize_stmt): Call remove_jump_threads_including on each outgoing edges when optimizing away a control statement. * gcc.c-torture/compile/pr67816.c: New test. Added: trunk/gcc/testsuite/gcc.c-torture/compile/pr67816.c Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-ssa-dom.c trunk/gcc/tree-ssa-threadupdate.c trunk/gcc/tree-ssa-threadupdate.h
prev parent reply other threads:[~2015-10-07 2:26 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-02 10:37 [Bug tree-optimization/67816] New: " rguenth at gcc dot gnu.org 2015-10-02 10:37 ` [Bug tree-optimization/67816] " rguenth at gcc dot gnu.org 2015-10-02 10:53 ` rguenth at gcc dot gnu.org 2015-10-02 11:10 ` mpolacek at gcc dot gnu.org 2015-10-02 12:01 ` rguenther at suse dot de 2015-10-04 7:01 ` rguenther at suse dot de 2015-10-05 8:16 ` rguenth at gcc dot gnu.org 2015-10-05 8:23 ` rguenth at gcc dot gnu.org 2015-10-05 8:26 ` rguenth at gcc dot gnu.org 2015-10-05 8:35 ` trippels at gcc dot gnu.org 2015-10-05 9:01 ` trippels at gcc dot gnu.org 2015-10-05 15:25 ` law at redhat dot com 2015-10-07 2:26 ` law at redhat dot com 2015-10-07 2:26 ` 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-67816-4-ZYULG78wOy@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).