Mobile Haskell: Compiling lazy functional programs for the Java Virtual Machine

Wakeling, David

doi:10.1007/bfb0056624

Cited by 7 publications

(6 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The only other work we are aware of in this area is that of Wakeling, one based on the G-Machine [8], which translates the G-code produced by HBC (the Haskell compiler developed at Chalmers) into Java bytecode; and one based on the ν, G machine [7] which compiles a core language into a set of ν, G instructions which are then transformed in Java bytecode, again using HBC. Both versions use a separate class, and hence a separate file, for each function, rather than each program, as with our compiler.…”

Section: Results and Other Workmentioning

confidence: 99%

“…There is also a compiler for Standard ML from Persimmon which compiles stand-alone SML programs to Java bytecode [15] ,but as this is for a strict language we do not include it in our comparisons. Table IV gives the running times for several programs using our compiler with both optimisations switched on, and using both Sun's JVM and the Kaffe Open VM [16] to run the generated class files; Wakeling's compiler (the ν, G -Machine version [7]) using Sun's JDK; the Haskell interpreter Hugs (version 1.4); and the Glasgow Haskell Compiler, GHC (version 2.10). The Haskell and Ginger sources were made as close as possible, but all the Haskell programs compiled using Wakeling's compiler have been explicitly mono-typed where appropriate.…”

Section: Results and Other Workmentioning

confidence: 99%

“…We then discuss the design of the run-time environment of our compiler and how we compile Ginger programs. We give some results of running programs compiled with our compiler, comparing them with Nottingham and Yale Haskell interpreter Hugs [5], the Glasgow Haskell Compiler [6] and another lazy functional program compiler, developed by David Wakeling at Exeter, which targets the JVM [8,7], and finally conclude.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Compiling lazy functional programs to Java bytecode

Meehan

Joy

1999

Softw: Pract. Exper.

View full text Add to dashboard Cite

The Java Virtual Machine (JVM) was designed as the target for Java compilers, but there is no reason why it cannot be used as the target for other languages. We describe the implementation of a compiler which translates a lazy, weakly-typed functional program into Java class files. We compare the performance of our compiler to the only other known compiler from a lazy functional language to the JVM. The results are broadly similar, suggesting that to get a significant performance speed-up using this compilation paradigm will come only from increasing the performance of the JVM, rather than enhancing the compiler itself.

show abstract

Section: Results and Other Workmentioning

confidence: 99%

Section: Results and Other Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Compiling lazy functional programs to Java bytecode

Meehan

Joy

1999

Softw: Pract. Exper.

View full text Add to dashboard Cite

show abstract

“…Despite problems mapping functional virtual machines onto these platforms various classes of functional language have taken this route, including sequential, concurrent, parallel, distributed and mobile languages. An early JVM-based sequential Haskell was produced by Wakeling (1997) and he has since produced a mobile Haskell (Wakeling, 1998). A JVM-based parallel Haskell similar to GpH has been implemented by Rauber du Bois (2001).…”

Section: Other Distributed Functional Languagesmentioning

confidence: 99%

Parallel and Distributed Haskells

2002

View full text Add to dashboard Cite

Parallel and distributed languages specify computations on multiple processors and have a computation language to describe the algorithm, i.e. what to compute, and a coordination language to describe how to organise the computations across the processors. Haskell has been used as the computation language for a wide variety of parallel and distributed languages, and this paper is a comprehensive survey of implemented languages. We outline parallel and distributed language concepts and classify Haskell extensions using them. Similar example programs are used to illustrate and contrast the coordination languages, and the comparison is facilitated by the common computation language. A lazy language is not an obvious choice for parallel or distributed computation, and we address the question of why Haskell is a common functional computation language.

show abstract

“…For example, the Java Virtual Machine, which provides garbage collection and exception handling, has been used as a target for languages other than Java, including Ada [36], ML [7], Scheme [12], and Haskell [39]. But a sophisticated platform like a virtual machine embodies too many design decisions.…”

Section: Introductionmentioning

confidence: 99%

C-—: A Portable Assembly Language that Supports Garbage Collection

Jones

Ramsey

Reig

1999

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. For a compiler writer, generating good machine code for a variety of platforms is hard work. One might try to reuse a retargetable code generator, but code generators are complex and difficult to use, and they limit one's choice of implementation language. One might try to use C as a portable assembly language, but C limits the compiler writer's flexibility and the performance of the resulting code. The wide use of C, despite these drawbacks, argues for a portable assembly language. C--is a new language designed expressly for this purpose. The use of a portable assembly language introduces new problems in the support of such high-level run-time services as garbage collection, exception handling, concurrency, profiling, and debugging. We address these problems by combining the C--language with a C--run-time interface. The combination is designed to allow the compiler writer a choice of sourcelanguage semantics and implementation techniques, while still providing good performance.

show abstract

Mobile Haskell: Compiling lazy functional programs for the Java Virtual Machine

Cited by 7 publications

References 8 publications

Compiling lazy functional programs to Java bytecode

Compiling lazy functional programs to Java bytecode

Parallel and Distributed Haskells

C-—: A Portable Assembly Language that Supports Garbage Collection

Contact Info

Product

Resources

About