Gordon Anderson wrote:
Simon Marlow wrote:
GHC will only cross-compile to architectures for which it already has a
native code generator. So cross-compiling won't help with porting, unless
you're prepared to write a native-code backend for the target first (and
even then, there's a lot more to cross-compiling than just making the
compiler emit .s for the target platform).
Whats the approach for new targets? ... eg -
Even if you have a cross compile working [ie. no ifdef XXX_TARGET ]...
you may also need, say, a 6.8 C-- version embedded in GHC source tree
to bootstrap
[ Im assuming C-- source can be built on a new target that has a C compiler? ]
No, you need .hc files (there isn't a widely-available C-- compiler that
could be used for porting).
But I'm optimistic that we can clean up the .hc-file bootstrapping story
when we change the build system to use more "make" and less Cabal. The
hard part is to keep it working, and for that we just need more automation.
We have a nightly build that runs in unregisterised mode (I haven't
looked at it for a while, we should make sure it's working for 6.10.1), and
it would be nice to have that build essentially do an automated bootstrap too.
Cheers,
Simon
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
