Related articles |
---|
[2 earlier articles] |
Re: register allocation: basic blocks, liveness and next use max@gustavus.edu (Max Hailperin) (2008-03-23) |
Re: register allocation: basic blocks, liveness and next use max@gustavus.edu (Max Hailperin) (2008-03-23) |
Re: register allocation: basic blocks, liveness and next use max@gustavus.edu (Max Hailperin) (2008-03-23) |
Re: register allocation: basic blocks, liveness and next use kevin.phillips83@yahoo.com (kphillips) (2008-03-23) |
Re: register allocation: basic blocks, liveness and next use gene.ressler@gmail.com (Gene) (2008-03-23) |
Re: register allocation: basic blocks, liveness and next use cfc@shell01.TheWorld.com (Chris F Clark) (2008-03-23) |
Re: register allocation: basic blocks, liveness and next use kevin.phillips83@yahoo.com (kphillips) (2008-03-27) |
Re: register allocation: basic blocks, liveness and next use jeffrey.kenton@comcast.net (Jeff Kenton) (2008-04-03) |
From: | kphillips <kevin.phillips83@yahoo.com> |
Newsgroups: | comp.compilers |
Date: | Thu, 27 Mar 2008 03:26:50 -0700 (PDT) |
Organization: | Compilers Central |
References: | 08-03-084 08-03-088 08-03-089 08-03-091 08-03-093 |
Keywords: | optimize |
Posted-Date: | 27 Mar 2008 23:59:32 EDT |
> I suspect most student
> compilers implement languages where not breaking a block at a call
> boundary solves the problem and they don't have any semantics where
> doing that causes things to break.
Thanks for your in-depth reply. I'm still relatively new to the area
and started off through books that are intended for academic courses.
Augmenting the grammar / features does in fact lead you to situations
not addressed by the same books (although most of the questions can be
answered in the dragon book ...). Still, this mailing list archive has
been a great resource so far in looking for answers and leads.
Regards,
K. Phillips
Return to the
comp.compilers page.
Search the
comp.compilers archives again.