From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8489 invoked by alias); 7 Oct 2004 22:16:01 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 8482 invoked from network); 7 Oct 2004 22:16:00 -0000 Received: from unknown (HELO mail.cs.umass.edu) (128.119.243.168) by sourceware.org with SMTP; 7 Oct 2004 22:16:00 -0000 Received: from localhost (IDENT:pLCs9ok+IZbJTVp6W91eCzOxhiCeqnWS@loki.cs.umass.edu [128.119.243.168]) by mail.cs.umass.edu (8.12.11/8.12.5) with ESMTP id i97MG03c009568; Thu, 7 Oct 2004 18:16:00 -0400 Date: Thu, 07 Oct 2004 22:16:00 -0000 Message-Id: <20041007.181556.07457730.kazu@cs.umass.edu> To: jakub@redhat.com Cc: rth@redhat.com, dnovillo@redhat.com, gcc-patches@gcc.gnu.org Subject: Re: [PATCH] Fix PR tree-optimization/17724 From: Kazu Hirata In-Reply-To: <20041007200445.GN31909@devserv.devel.redhat.com> References: <20041007200445.GN31909@devserv.devel.redhat.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-10/txt/msg00689.txt.bz2 Hi Jakub, > The first patch calls free_dominance_info in cleanup_tree_cfg whenever > delete_unreachable_blocks deleted some basic blocks. It should be safe, but > might be expensive. I guess so. thread_jumps, which is called right after delete_unreachable_blocks in cleanup_tree_cfg, tries to maintain the dominator info, so if you are freeing it, you might want to remove the code to maintain it in thread_jumps. Kazu Hirata