From: Matt Wette <matt.wette@gmail.com>
To: guile-devel@gnu.org
Subject: Re: flow-analysis and Offner's notes
Date: Sat, 9 Jun 2018 08:20:57 -0700 [thread overview]
Message-ID: <79773674-92b2-5d0a-190b-434ef5a39554@gmail.com> (raw)
In-Reply-To: <85a2a273-6e21-9f57-3a43-b32607a811f3@gmail.com>
On 06/09/2018 06:34 AM, Matt Wette wrote:
> On 06/08/2018 05:17 PM, Matt Wette wrote:
>> Andy Windo's blog on flow-analysis in Guile references Offner's
>> "Notes on Graph
>> Algorithms Used in Optimizing Compilers"? Anyone read this
>> manuscript? Lemma
>> 2.2 says, in a flow-graph, if x>>z and y>>z, then either x>>y or
>> y>>x. The proof
>> uses the argument that the path from s, the start, to z has to
>> include both x and y.
>> I'm not seeing that. Consider a graph s->x, s->y, x->z and y->z.
>> What am I missing?
I was missing the definition of "dominates."
Sorry for the interruption.
Now need to think about this.
prev parent reply other threads:[~2018-06-09 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-09 0:17 flow-analysis and Offner's notes Matt Wette
2018-06-09 13:34 ` Matt Wette
2018-06-09 15:20 ` Matt Wette [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=79773674-92b2-5d0a-190b-434ef5a39554@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-devel@gnu.org \
/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).