From: meissner@cygnus.com
To: amylaar@cygnus.co.uk, law@cygnus.com
Cc: egcs@cygnus.com, jason@cygnus.com, tot@trema.com
Subject: Re: Flow analysis confused by exception handling
Date: Wed, 03 Dec 1997 04:36:00 -0000 [thread overview]
Message-ID: <199712031235.HAA21670@tweedledumb.cygnus.com> (raw)
| The schedulers rely on basic_block_{head,end} do delimit basic block
| boundaries. Similarly for most passes after flow.
Just a reminder, this is true for the passes after flow and up to reload.
Reload seriously damages the flow information (insns created by reload that are
adjacent to basic blocks, won't be added to any basic block).
next reply other threads:[~1997-12-03 4:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-03 4:36 meissner [this message]
[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
-- 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=199712031235.HAA21670@tweedledumb.cygnus.com \
--to=meissner@cygnus.com \
--cc=amylaar@cygnus.co.uk \
--cc=egcs@cygnus.com \
--cc=jason@cygnus.com \
--cc=law@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).