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/67892] [5/6 Regression] Wrong code at -O1 and above Date: Thu, 29 Oct 2015 16:20:00 -0000 [thread overview] Message-ID: <bug-67892-4-qBIRzUCVS2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67892-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67892 --- Comment #3 from Jeffrey A. Law <law at gcc dot gnu.org> --- Author: law Date: Thu Oct 29 16:20:06 2015 New Revision: 229538 URL: https://gcc.gnu.org/viewcvs?rev=229538&root=gcc&view=rev Log: [PATCH][PR tree-optimization/67892] Use FSM threader to handle backedges PR tree-optimization/67892 * tree-ssa-threadedge.c (simplify_controL_stmt_condition): Fix typo in comment. (thread_through_normal_block): If we have seen a backedge, then do nothing. No longer call find_jump_threads_backwards here. (thread_across_edge): Use find_jump_threads_backwards to find jump threads if the old style threader was not successful. * tree-ssa-threadbackward.c (get_gimple_control_stmt): Use gsi_last_nondebug_bb. Return NULL if the block does not end with a control statement. (find_jump_threads_backwards): Setup code moved here from tree-ssa-threadedge.c::thread_through_normal_block. Accept single edge argument instead of name & block. * tree-ssa-threadbackward.h (find_jump_threads_backwards): Update prototype. PR tree-optimization/67892 * gcc.dg/tree-ssa/pr21417: Update expected output. * gcc.dg/tree-ssa/ssa-dom-thread-2b.c: Likewise. Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.dg/tree-ssa/pr21417.c trunk/gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-thread-2b.c trunk/gcc/tree-ssa-threadbackward.c trunk/gcc/tree-ssa-threadbackward.h trunk/gcc/tree-ssa-threadedge.c
next prev parent reply other threads:[~2015-10-29 16:20 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-08 9:34 [Bug translation/67892] New: " sikkins at hotmail dot com 2015-10-08 11:44 ` [Bug translation/67892] [5/6 Regression] " rguenth at gcc dot gnu.org 2015-10-09 22:47 ` law at redhat dot com 2015-10-29 16:20 ` law at gcc dot gnu.org [this message] 2015-10-29 16:21 ` [Bug tree-optimization/67892] " law at redhat dot com
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-67892-4-qBIRzUCVS2@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).