public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/50908] [4.7 Regression] building emacs-23.3; gives msg: indent.c:1140:1: internal compiler error: in verify_dominators, at dominance.c:1041 Date: Tue, 01 Nov 2011 12:43:00 -0000 [thread overview] Message-ID: <bug-50908-4-P7RVOrsEcc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50908-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50908 --- Comment #6 from vries at gcc dot gnu.org 2011-11-01 12:42:06 UTC --- Author: vries Date: Tue Nov 1 12:42:01 2011 New Revision: 180737 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=180737 Log: 2011-11-01 Tom de Vries <tom@codesourcery.com> PR tree-optimization/50908 * tree-ssa-tail-merge.c (update_vuses): Now that edges are removed before update_vuses, test for 1 predecessor rather than two. (delete_block_update_dominator_info): New function, part of it factored out of ... (replace_block_by): Use delete_block_update_dominator_info. Call update_vuses after deleting bb1 and updating dominator info, instead of before. Modified: trunk/gcc/ChangeLog trunk/gcc/tree-ssa-tail-merge.c
next prev parent reply other threads:[~2011-11-01 12:43 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-29 0:46 [Bug c/50908] New: " grgoffe at yahoo dot com 2011-10-29 18:15 ` [Bug c/50908] " gjl at gcc dot gnu.org 2011-10-30 9:17 ` [Bug tree-optimization/50908] [4.7 Regression] " rguenth at gcc dot gnu.org 2011-10-30 9:39 ` vries at gcc dot gnu.org 2011-10-31 9:42 ` vries at gcc dot gnu.org 2011-10-31 13:54 ` joel at gcc dot gnu.org 2011-10-31 14:05 ` vries at gcc dot gnu.org 2011-11-01 12:43 ` vries at gcc dot gnu.org [this message] 2011-11-01 21:48 ` vries at gcc dot gnu.org 2011-11-01 21:50 ` vries at gcc dot gnu.org 2011-11-01 21:51 ` vries at gcc dot gnu.org 2011-11-01 21:52 ` vries at gcc dot gnu.org 2011-11-02 23:52 ` grgoffe at yahoo 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-50908-4-P7RVOrsEcc@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).