On Thu, May 31, 2007 at 12:10:06AM +0100, Neil Mitchell wrote:
From Alexis:
Hi Neil,
I got your email from the YHC website, and I have several questions which I hope you can answer for me. I am an MSc student working on the development of a Haskell system for use with the Lego Mindstorms NXT (My intent is to port it using the GCC-ARM toolchain and get it running with the NXT firmware). For the most part I need a Haskell compiler that will run within the 256KB memory space. YHc seems like it could be perfect for such an application, but I am curious about the following:
- Is YHc [sic] VM based? Or can it compile Haskell directly to C code, or both, or some intermediate code?
It currently uses a stack bytecode machine by default, and it can compile to two intermediate forms (PosLambda, which you don't want to know any more about, and Yhc.Core, a simple and orthogonal IR designed for use by external tools such as compiler backends) Neil Mitchell is working on a ultra-optimizing C backend for Yhc. Frankly this incongruity scares me.
- What is the typical memory footprint of the compiler/programs? Especially the interpreter/VM...? (I'm trying to compare this to GHc, for instance)
Thanks in advance for your kind response.
Cheers, -- </Alexis> _______________________________________________ Yhc mailing list Yhc@haskell.org http://www.haskell.org/mailman/listinfo/yhc