public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
Cc: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>,
	gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: Peeling loops at tree level?, Lno branch merge patches ping
Date: Mon, 20 Sep 2004 20:41:00 -0000	[thread overview]
Message-ID: <20040920194310.GB26387@redhat.com> (raw)
In-Reply-To: <20040916220116.GA806@atrey.karlin.mff.cuni.cz>

On Fri, Sep 17, 2004 at 12:01:16AM +0200, Zdenek Dvorak wrote:
> +   make_edge (new_head, second_head, EDGE_FALSE_VALUE);
...
> +   /* When edge 'e' was split, it created a fall through edge
> +       from new head to second head. Above created FALSE edge
> +       from new head to second head and now we do not need the
> +       fall through edge.  */
> +   for (e0 = new_head->succ; e0; e0 = e0->succ_next)
> +     if (e0->dest == second_head)
> +       e0->flags &= ~EDGE_FALLTHRU;

  e0 = make_edge (new_head, second_head, EDGE_FALSE_VALUE);


Otherwise ok.


r~

  reply	other threads:[~2004-09-20 19:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-13 14:34 Peeling loops at tree level? Richard Guenther
2004-09-13 14:40 ` Richard Guenther
2004-09-13 14:57   ` Zdenek Dvorak
     [not found]     ` <Pine.LNX.4.44.0409131647340.9036-100000@alwazn.tat.physik.uni-tuebingen.de>
2004-09-13 15:49       ` Peeling loops at tree level?, Lno branch merge patches ping Zdenek Dvorak
2004-09-16  2:21         ` Richard Henderson
2004-09-16  2:44         ` Richard Henderson
2004-09-16 23:05           ` Zdenek Dvorak
2004-09-20 20:41             ` Richard Henderson [this message]
2004-09-16  2:46         ` Richard Henderson

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=20040920194310.GB26387@redhat.com \
    --to=rth@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=rakdver@atrey.karlin.mff.cuni.cz \
    --cc=rguenth@tat.physik.uni-tuebingen.de \
    /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).