From: Steven Bosscher <stevenb@suse.de>
To: Andrew MacLeod <amacleod@redhat.com>
Cc: Jeff Law <law@redhat.com>, gcc-patches <gcc-patches@gcc.gnu.org>,
Diego Novillo <dnovillo@redhat.com>
Subject: Re: Fix a tcb crash and a potential bug on mainline
Date: Wed, 20 Oct 2004 14:30:00 -0000 [thread overview]
Message-ID: <200410201559.15021.stevenb@suse.de> (raw)
In-Reply-To: <1098279673.5695.3937.camel@pain>
On Wednesday 20 October 2004 15:41, Andrew MacLeod wrote:
> Why doesnt cleanup_control_flow actually follow the flow from entry to
> exit instead of FOR_EACH_BB?
I'm asking myself that each time I see FOR_{EACH,ALL}_BB.
> Does it have to do something in blocks
> that are unreachable?
No.
> Or is it just an attempt to avoid using a visited
> bitmap?
And a stack for backtracking.
I've been thinking for some time now about implementing FOR_EACH_BB_DFS
(and perhaps other visiting orders) using some iterator. You think that
would be a good idea?
Gr.
Steven
next prev parent reply other threads:[~2004-10-20 13:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 21:09 Steven Bosscher
2004-10-18 22:06 ` Andrew MacLeod
2004-10-18 22:18 ` Andrew Pinski
2004-10-19 20:58 ` Jeffrey A Law
2004-10-19 21:29 ` Steven Bosscher
2004-10-19 22:08 ` Jeffrey A Law
2004-10-19 22:27 ` Daniel Berlin
2004-10-19 22:35 ` Jeffrey A Law
2004-10-19 23:08 ` Daniel Berlin
2004-10-19 23:14 ` Daniel Berlin
2004-10-21 2:33 ` Jeffrey A Law
2004-10-19 22:36 ` Steven Bosscher
2004-10-19 22:41 ` Diego Novillo
2004-10-19 23:16 ` Jeffrey A Law
2004-10-20 13:17 ` Andrew MacLeod
2004-10-20 13:32 ` Steven Bosscher
2004-10-20 13:47 ` Andrew MacLeod
2004-10-20 14:30 ` Steven Bosscher [this message]
2004-10-20 16:53 ` Andrew MacLeod
2004-10-20 17:33 ` Daniel Berlin
2004-10-22 19:15 ` Jeffrey A Law
2004-10-22 19:33 ` Steven Bosscher
2004-10-22 19:37 ` Jeffrey A Law
2004-10-22 19:40 ` Steven Bosscher
2004-10-22 21:08 ` Jeffrey A Law
2004-10-24 21:20 ` Steven Bosscher
2004-10-27 16:27 ` Jeffrey A Law
2004-10-22 19:10 ` Jeffrey A Law
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=200410201559.15021.stevenb@suse.de \
--to=stevenb@suse.de \
--cc=amacleod@redhat.com \
--cc=dnovillo@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@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).