On 26 January 2005 16:54, Norman Ramsey wrote:
> I'm not really qualified to comment on this narrow issue, but I'm
> aware of a heavyweight solution that helps make this and similar
> problems go away---in most compilers I have worked on, we have
> eventually made the shift to loading all targets at once in a single
> binary. The compiler's target is then selected on the command line,
> when the compiler is run. If planned for in advance, this strategy is
> fairly simple to implement and saves enormous effort in configuration
> management. If not planned for in advance, it can be painful to
> switch---I remember, for example, helping to make the transition from
> lcc 2 to lcc 3. If you want to see how it is handled in lcc, this is
> covered pretty well in the book.
>
> I realize this is more radical than any of the alternatives you are
> asking about, but I thought it was something you might like to have in
> the back of your mind in case you ever do a significant refactoring of
> your build setup.
Agreed, I think approach has a lot to be said for it. I can't quite
bring myself to do it, though :-) In particular there'd be a lot of
keyboard-bashing in the native code gen to do.
I suppose ideally we should have runtime-pluggable native code
generators. That addresses the complaint of having a huge compiler
binary, and we have the technology.
Cheers,
Simon
_______________________________________________
Cvs-ghc mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/cvs-ghc
