public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/46177] [4.5 Regression] ICE: in prop_phis, at tree-loop-distribution.c:327 with -fno-tree-copy-prop -ftree-loop-distribution Date: Fri, 12 Nov 2010 15:30:00 -0000 [thread overview] Message-ID: <bug-46177-4-PfBhMSoZjf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46177-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46177 --- Comment #10 from Richard Guenther <rguenth at gcc dot gnu.org> 2010-11-12 14:43:25 UTC --- Author: rguenth Date: Fri Nov 12 14:43:19 2010 New Revision: 166652 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=166652 Log: 2010-11-12 Richard Guenther <rguenther@suse.de> Backport from mainline 2010-11-09 Richard Guenther <rguenther@suse.de> PR tree-optimization/46355 * tree-loop-distribution.c (tree_loop_distribution): Do not distribute loops without a single exit. * gcc.dg/pr46355.c: New testcase. 2010-11-02 Richard Guenther <rguenther@suse.de> PR tree-optimization/46177 * tree-loop-distribution.c (prop_phis): Use mark_virtual_phi_result_for_renaming. * gcc.dg/pr46177.c: New testcase. 2010-11-09 Richard Guenther <rguenther@suse.de> PR tree-optimization/46177 * tree-loop-distribution.c (prop_phis): Remove. (generate_builtin): Re-use the old loop exit edge to avoid needing to update PHI nodes. * gcc.dg/pr46177-2.c: New testcase. Added: branches/gcc-4_5-branch/gcc/testsuite/gcc.dg/pr46177-2.c branches/gcc-4_5-branch/gcc/testsuite/gcc.dg/pr46177.c branches/gcc-4_5-branch/gcc/testsuite/gcc.dg/pr46355.c Modified: branches/gcc-4_5-branch/gcc/ChangeLog branches/gcc-4_5-branch/gcc/testsuite/ChangeLog branches/gcc-4_5-branch/gcc/tree-loop-distribution.c
next prev parent reply other threads:[~2010-11-12 15:30 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-25 23:45 [Bug tree-optimization/46177] New: [4.5/4.6 " zsojka at seznam dot cz 2010-10-26 7:06 ` [Bug tree-optimization/46177] " hjl.tools at gmail dot com 2010-10-26 13:57 ` rguenth at gcc dot gnu.org 2010-10-27 1:58 ` jakub at gcc dot gnu.org 2010-11-02 13:38 ` rguenth at gcc dot gnu.org 2010-11-02 15:45 ` rguenth at gcc dot gnu.org 2010-11-02 15:49 ` [Bug tree-optimization/46177] [4.5 " rguenth at gcc dot gnu.org 2010-11-05 21:37 ` zsojka at seznam dot cz 2010-11-05 22:38 ` rguenther at suse dot de 2010-11-09 15:02 ` [Bug tree-optimization/46177] [4.5/4.6 " rguenth at gcc dot gnu.org 2010-11-09 15:03 ` [Bug tree-optimization/46177] [4.5 " rguenth at gcc dot gnu.org 2010-11-12 15:24 ` rguenth at gcc dot gnu.org 2010-11-12 15:30 ` rguenth at gcc dot gnu.org [this message] 2010-11-12 22:00 ` jakub 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-46177-4-PfBhMSoZjf@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).