public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>,
	Richard Henderson <rth@redhat.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix PR tree-optimization/17724 (take 2)
Date: Tue, 12 Oct 2004 17:59:00 -0000	[thread overview]
Message-ID: <1097603898.7614.85.camel@localhost.localdomain> (raw)
In-Reply-To: <20041010145645.GZ31909@devserv.devel.redhat.com>

On Sun, 2004-10-10 at 10:56, Jakub Jelinek wrote:

> 	PR tree-optimization/17724
> 	* tree-cfg.c (tree_purge_dead_eh_edges): Free dominance info.
> 
Zdenek raised a good point re EH edges and dominance info.  Lets take
the safe approach for now.  This is OK.


Diego.

  reply	other threads:[~2004-10-12 17:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20041009082440.GB22455@atrey.karlin.mff.cuni.cz>
2004-10-09  9:23 ` [PATCH] Fix PR tree-optimization/17724 Zdenek Dvorak
2004-10-10 15:20   ` [PATCH] Fix PR tree-optimization/17724 (take 2) Jakub Jelinek
2004-10-12 17:59     ` Diego Novillo [this message]
2004-10-15 19:24     ` Zdenek Dvorak

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=1097603898.7614.85.camel@localhost.localdomain \
    --to=dnovillo@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=rakdver@atrey.karlin.mff.cuni.cz \
    --cc=rth@redhat.com \
    /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: link
Be 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).