public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/65735] [5 Regression] ICE (in duplicate_thread_path, at tree-ssa-threadupdate.c) Date: Sat, 11 Apr 2015 17:33:00 -0000 [thread overview] Message-ID: <bug-65735-4-ShNz0KEMVq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65735-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65735 --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Author: jakub Date: Sat Apr 11 17:32:54 2015 New Revision: 222011 URL: https://gcc.gnu.org/viewcvs?rev=222011&root=gcc&view=rev Log: PR tree-optimization/65735 * tree-ssa-threadedge.c (fsm_find_control_statement_thread_paths): Remove visited_phis argument, add visited_bbs, avoid recursing into the same bb rather than just into the same phi node. (thread_through_normal_block): Adjust caller. * gcc.c-torture/compile/pr65735.c: New test. Added: trunk/gcc/testsuite/gcc.c-torture/compile/pr65735.c Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-ssa-threadedge.c
next prev parent reply other threads:[~2015-04-11 17:33 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-10 21:37 [Bug middle-end/65735] New: [5 Regression] ICE (in duplicate_thread_path, at tree-ssa-threadupdate.c) on arm-linux-gnueabihf doko at gcc dot gnu.org 2015-04-10 23:22 ` [Bug middle-end/65735] [5 Regression] ICE (in duplicate_thread_path, at tree-ssa-threadupdate.c) doko at gcc dot gnu.org 2015-04-10 23:27 ` jakub at gcc dot gnu.org 2015-04-11 8:59 ` jakub at gcc dot gnu.org 2015-04-11 10:07 ` jakub at gcc dot gnu.org 2015-04-11 14:22 ` jakub at gcc dot gnu.org 2015-04-11 17:33 ` jakub at gcc dot gnu.org [this message] 2015-04-12 19:12 ` jakub at gcc dot gnu.org 2015-10-28 9:01 ` yroux 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-65735-4-ShNz0KEMVq@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).