public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "yroux at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/65048] [5 Regression] ICE in add_phi_args_after_copy_edge, at tree-cfg.c Date: Wed, 28 Oct 2015 09:01:00 -0000 [thread overview] Message-ID: <bug-65048-4-9rjdWT5M3h@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65048-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65048 --- Comment #7 from Yvan Roux <yroux at gcc dot gnu.org> --- Author: yroux Date: Wed Oct 28 09:00:47 2015 New Revision: 229478 URL: https://gcc.gnu.org/viewcvs?rev=229478&root=gcc&view=rev Log: gcc/ 2015-10-28 Yvan Roux <yvan.roux@linaro.org> Sebastian Pop <s.pop@samsung.com> Backport from trunk r221007, r221675, r222011. 2015-04-11 Jakub Jelinek <jakub@redhat.com> 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. 2015-03-25 Sebastian Pop <s.pop@samsung.com> PR tree-optimization/65177 * tree-ssa-threadupdate.c (verify_seme): Renamed verify_jump_thread. (bb_in_bbs): New. (duplicate_seme_region): Renamed duplicate_thread_path. Redirect all edges not adjacent on the path to the original code. 2015-02-26 Sebastian Pop <s.pop@samsung.com> PR tree-optimization/65048 * tree-ssa-threadupdate.c (valid_jump_thread_path): New. (thread_through_all_blocks): Call valid_jump_thread_path. Remove invalid FSM jump-thread paths. gcc/testsuite/ 2015-10-28 Yvan Roux <yvan.roux@linaro.org> Sebastian Pop <s.pop@samsung.com> Backport from trunk r221007, r221675, r222011. 2015-04-11 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/65735 * gcc.c-torture/compile/pr65735.c: New test. 2015-03-25 Sebastian Pop <s.pop@samsung.com> PR tree-optimization/65177 * gcc.dg/tree-ssa/ssa-dom-thread-10.c: New. 2015-02-26 Sebastian Pop <s.pop@samsung.com> PR tree-optimization/65048 * gcc.dg/tree-ssa/ssa-dom-thread-9.c: New. Added: branches/linaro/gcc-4_9-branch/gcc/testsuite/gcc.c-torture/compile/pr65735.c branches/linaro/gcc-4_9-branch/gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-thread-10.c branches/linaro/gcc-4_9-branch/gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-thread-9.c Modified: branches/linaro/gcc-4_9-branch/gcc/ChangeLog.linaro branches/linaro/gcc-4_9-branch/gcc/testsuite/ChangeLog.linaro branches/linaro/gcc-4_9-branch/gcc/tree-ssa-threadedge.c branches/linaro/gcc-4_9-branch/gcc/tree-ssa-threadupdate.c
prev parent reply other threads:[~2015-10-28 9:01 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-13 0:02 [Bug target/65048] New: [5 Regression] ICE in add_phi_args_after_copy_edge, at tree-cfg.c on arm-linux-gnueabihf doko at gcc dot gnu.org 2015-02-13 9:17 ` [Bug middle-end/65048] " rguenth at gcc dot gnu.org 2015-02-13 11:57 ` [Bug middle-end/65048] [5 Regression] ICE in add_phi_args_after_copy_edge, at tree-cfg.c jakub at gcc dot gnu.org 2015-02-13 17:56 ` spop at gcc dot gnu.org 2015-02-24 9:42 ` jakub at gcc dot gnu.org 2015-02-26 14:52 ` law at gcc dot gnu.org 2015-02-26 14:55 ` law at redhat dot com 2015-02-26 15:03 ` law at redhat dot com 2015-02-27 15:15 ` jakub at gcc dot gnu.org 2015-10-28 9:01 ` yroux 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-65048-4-9rjdWT5M3h@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).