Dan Mead wrote:
has there been any movement on this topic? i'm also interested in haskell on arm


do you guys thing telling ghc to emit C and then compiling that for arm is a better route than
getting direct compilation to work?


If you look on the GHC-on-ARM page[1], you'll find my attempts to bootstrap GHC 6.6 (the last version where cross-compiling GHC actually worked) to ARM.

The only success I had was in using jhc (not GHC) to generate portable C, which cross-compiled and ran fine (on my Nokia N810). GHC's C wouldn't compile out of the box, and I'm not sure what libraries or other hackery is required to make it do so.

Details of the failed cross-compilation and success with jhc are on the wiki page[1].

I'd love to have this working, but I have no time at all this term.


Braden Shepherdson
shepheb

[1] http://hackage.haskell.org/trac/ghc/wiki/ArmLinuxGhc



-dan

On Fri, Jul 25, 2008 at 3:55 AM, Simon Marlow <[email protected] <mailto:[email protected]>> wrote:

    Joe Buehler wrote:

        Simon Marlow wrote:

            For the registerised port, you really need a native code
            generator (the mangler is on death row, yay).  At a rough
            guess, I'd say porting the NCG would take a couple of weeks
            or so for someone unfamiliar with the code. Hopefully we'll
            improve that when we refactor the NCG as part of the backend
            overhaul.


        Is there any documentation on the NCG?  I ported 6.6 to HPUX 11
        some time ago
        and looked at the NCG but didn't do it for PA-RISC because it
        was going to take too
        much time to understand.  I was leaning towards the approach of
        trying to translate
        the code generator for another processor into PA-RISC.


    There's some old documentation, some of it is still relevant but
    probably much of it is out of date now:

    http://darcs.haskell.org/ghc/docs/comm/the-beast/ncg.html

    the best doc is the code, I'm afraid (but it has lot of illuminating
    comments and you can get a long way with cut-and-paste).

    Cheers,
           Simon

    _______________________________________________
    Haskell-Cafe mailing list
    [email protected] <mailto:[email protected]>
    http://www.haskell.org/mailman/listinfo/haskell-cafe



------------------------------------------------------------------------

_______________________________________________
Haskell-Cafe mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/haskell-cafe

_______________________________________________
Haskell-Cafe mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/haskell-cafe

Reply via email to