public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/17044] [3.5 Regression] libgcc2.c:169: internal compiler error: Segmentation fault Date: Mon, 16 Aug 2004 04:18:00 -0000 [thread overview] Message-ID: <20040816041836.2033.qmail@sourceware.org> (raw) In-Reply-To: <20040816015952.17044.danglin@gcc.gnu.org> ------- Additional Comments From danglin at gcc dot gnu dot org 2004-08-16 04:18 ------- Ok, after backporting the darwin fix, it turns out that the patch that actually introduced the ICE noted in the summary is: 2004-08-09 Jeff Law <law@redhat.com> * Makefile.in (OBJC-common): Add tree-ssa-threadupdate.c (tree-ssa-threadupdate.o): Add dependencies. * tree-ssa-threadupdate.c: New file. * tree-flow.h (incoming_edge_threaded): New flag in block annotation. (rewrite_vars_out_of_ssa): Remove prototype. (cleanup_tree_cfg): Returns a bool. * tree.h (thread_through_all_blocks): Prototype. * tree-outof-ssa.c (SSANORM_*): Move into here. (remove_ssa_form): Now static. (rewrite_vars_out_of_ssa): Kill. * tree-ssa-live.c (register_ssa_partitions_for_vars): Kill. * tree-ssa-live.h (SSANORM_*): Moved into tree-outof-ssa.c. (remove_ssa_form, register_partitions_for_vars): Kill declarations. * tree-cfg.c (cleanup_tree_cfg): Return a value indicating if anything was changed. * tree-phinodes.c (add_phi_arg): Get the block for the PHI from the PHI's annotation rather than the edge associated with the new argument. * tree-ssa-dom.c (redirection_edges): Kill. (redirect_edges_and_update_ssa_graph): Kill. (tree_ssa_dominator_optimize): Do not reset forwardable flag for blocks anymore. Do not initialize redirection_edges. Call thread_through_all_blocks. Simplify code for cleanup of the CFG and iterating. No longer call cleanup_tree_cfg outside the iteration loop. (thread_across_edge): No longer mess with forwardable blocks. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |law at redhat dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17044
next prev parent reply other threads:[~2004-08-16 4:18 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-16 1:59 [Bug middle-end/17044] New: " danglin at gcc dot gnu dot org 2004-08-16 2:03 ` [Bug middle-end/17044] [3.5 Regression] " pinskia at gcc dot gnu dot org 2004-08-16 2:11 ` dave at hiauly1 dot hia dot nrc dot ca 2004-08-16 4:18 ` danglin at gcc dot gnu dot org [this message] 2004-08-16 6:07 ` law at redhat dot com 2004-08-16 14:40 ` danglin at gcc dot gnu dot org 2004-08-17 5:26 ` pinskia at gcc dot gnu dot org 2004-08-17 5:44 ` law at redhat dot com 2004-08-17 16:27 ` dave at hiauly1 dot hia dot nrc dot ca 2004-08-17 17:38 ` dave at hiauly1 dot hia dot nrc dot ca 2004-08-17 20:49 ` dave at hiauly1 dot hia dot nrc dot ca 2004-08-18 15:36 ` pinskia at gcc dot gnu dot org 2004-08-24 19:48 ` law at redhat dot com 2004-08-24 20:00 ` dave at hiauly1 dot hia dot nrc dot ca 2004-08-24 20:04 ` law at redhat dot com 2004-08-24 20:59 ` cvs-commit at gcc dot gnu dot org 2004-08-24 21:04 ` pinskia at gcc dot gnu dot 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=20040816041836.2033.qmail@sourceware.org \ --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).