| dc.contributor.advisor | Hetland, Magnus Lie | nb_NO |
| dc.contributor.author | Thomassen, Even Wiik | nb_NO |
| dc.date.accessioned | 2014-12-19T13:39:33Z | |
| dc.date.available | 2014-12-19T13:39:33Z | |
| dc.date.created | 2013-04-28 | nb_NO |
| dc.date.issued | 2013 | nb_NO |
| dc.identifier | 618488 | nb_NO |
| dc.identifier | ntnudaim:8175 | nb_NO |
| dc.identifier.uri | http://hdl.handle.net/11250/253137 | |
| dc.description.abstract | 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. | nb_NO |
| dc.language | eng | nb_NO |
| dc.publisher | Institutt for datateknikk og informasjonsvitenskap | nb_NO |
| dc.title | Trace-based just-in-time compiler for Haskell with RPython | nb_NO |
| dc.type | Master thesis | nb_NO |
| dc.source.pagenumber | 94 | nb_NO |
| dc.contributor.department | Norges teknisk-naturvitenskapelige universitet, Fakultet for informasjonsteknologi, matematikk og elektroteknikk, Institutt for datateknikk og informasjonsvitenskap | nb_NO |
