Trace-based just-in-time compiler for Haskell with RPython
Can Haskell benefit from tracing JIT optimization techniques, and is the RPython translation toolchain suitable for purely functional, lazy languages such as Haskell? RPython has been used to implement VMs for many different programming languages, but not for any purely functional or lazy languages....
Main Author: | |
---|---|
Format: | Others |
Language: | English |
Published: |
Norges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskap
2013
|
Online Access: | http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-20779 |
id |
ndltd-UPSALLA1-oai-DiVA.org-ntnu-20779 |
---|---|
record_format |
oai_dc |
spelling |
ndltd-UPSALLA1-oai-DiVA.org-ntnu-207792013-06-23T04:11:27ZTrace-based just-in-time compiler for Haskell with RPythonengThomassen, Even WiikNorges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskapInstitutt for datateknikk og informasjonsvitenskap2013Can Haskell benefit from tracing JIT optimization techniques, and is the RPython translation toolchain suitable for purely functional, lazy languages such as Haskell? RPython has been used to implement VMs for many different programming languages, but not for any purely functional or lazy languages. Haskell has achieved impressive speed with ahead-of-time optimizations. Attempts at trace-based JIT optimizations of Haskell have so far not achieved greater speed than static compilation. PyHaskell, a prototype Haskell VM with a meta-tracing JIT compiler written in RPython, shows that the RPython toolchain is suitable for Haskell. While the meta-tracer greatly speeds up PyHaskell, it does not yet beat GHC. Student thesisinfo:eu-repo/semantics/bachelorThesistexthttp://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-20779Local ntnudaim:8175application/pdfinfo:eu-repo/semantics/openAccess |
collection |
NDLTD |
language |
English |
format |
Others
|
sources |
NDLTD |
description |
Can Haskell benefit from tracing JIT optimization techniques, and is the RPython translation toolchain suitable for purely functional, lazy languages such as Haskell? RPython has been used to implement VMs for many different programming languages, but not for any purely functional or lazy languages. Haskell has achieved impressive speed with ahead-of-time optimizations. Attempts at trace-based JIT optimizations of Haskell have so far not achieved greater speed than static compilation. PyHaskell, a prototype Haskell VM with a meta-tracing JIT compiler written in RPython, shows that the RPython toolchain is suitable for Haskell. While the meta-tracer greatly speeds up PyHaskell, it does not yet beat GHC. |
author |
Thomassen, Even Wiik |
spellingShingle |
Thomassen, Even Wiik Trace-based just-in-time compiler for Haskell with RPython |
author_facet |
Thomassen, Even Wiik |
author_sort |
Thomassen, Even Wiik |
title |
Trace-based just-in-time compiler for Haskell with RPython |
title_short |
Trace-based just-in-time compiler for Haskell with RPython |
title_full |
Trace-based just-in-time compiler for Haskell with RPython |
title_fullStr |
Trace-based just-in-time compiler for Haskell with RPython |
title_full_unstemmed |
Trace-based just-in-time compiler for Haskell with RPython |
title_sort |
trace-based just-in-time compiler for haskell with rpython |
publisher |
Norges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskap |
publishDate |
2013 |
url |
http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-20779 |
work_keys_str_mv |
AT thomassenevenwiik tracebasedjustintimecompilerforhaskellwithrpython |
_version_ |
1716589845407596544 |