From: Jeffrey A Law <law@cygnus.com>
To: Joern Rennecke <amylaar@cygnus.co.uk>
Cc: jason@cygnus.com (Jason Merrill), tot@trema.com, egcs@cygnus.com
Subject: Re: Flow analysis confused by exception handling
Date: Tue, 02 Dec 1997 16:29:00 -0000 [thread overview]
Message-ID: <13578.881108687@cygnus.com> (raw)
In-Reply-To: <199712022112.VAA14078@phal.cygnus.co.uk>
In message < 199712022112.VAA14078@phal.cygnus.co.uk >you write:
> > Tue Dec 2 01:42:33 1997 Jason Merrill <jason@yorick.cygnus.com>
> >
> > * flow.c (find_basic_blocks): A CALL_INSN that can throw starts
> > a new basic block.
> > (find_basic_blocks_1): Likewise.
>
> I think you have to fix some code in the schedulers when you do that.
I don't think so.
The schedulers rely on basic_block_{head,end} do delimit basic block
boundaries. Similarly for most passes after flow.
jeff
next prev parent reply other threads:[~1997-12-02 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199712020947.KAA05490.cygnus.egcs@lev.labs.trema.com>
1997-12-02 2:25 ` Jason Merrill
1997-12-02 13:14 ` Joern Rennecke
1997-12-02 16:29 ` Jeffrey A Law [this message]
1997-12-03 4:36 meissner
-- strict thread matches above, loose matches on Subject: below --
1997-12-02 1:47 Teemu Torma
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=13578.881108687@cygnus.com \
--to=law@cygnus.com \
--cc=amylaar@cygnus.co.uk \
--cc=egcs@cygnus.com \
--cc=jason@cygnus.com \
--cc=tot@trema.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).