![]() |
CiteULike | ![]() |
zednenem's CiteULike | ![]() |
![]() |
|
![]() |
Register | ![]() |
Log in | ![]() |
Phase Distinctions In The Compilation Of Epigramby: James Mckinna, Edwin Brady
|
Reviews
[Write a review of this article]
Find related articles from these CiteULike users
Find related articles with these CiteULike tags
Posting History
AbstractWe describe the execution of Epigram on a stock architecture such as the G-machine, compiling via a core type theory and a supercombinator language. We show, via optimising transformations on the core type theory, that unused or duplicated values can be erased at run-time. Thus there exists a phase distinction, not between types and values, but between values which are used at compile-time only and values which are used at run-time. Through a simple example, lookup of a value in a sized vector, we show how our optimisations remove compile-time only values from terms and, furthermore, how we can use straightforward static analysis with our rich type information to avoid the need for any run-time bounds check when executing the lookup function.
BibTeX record
RIS record