Would it be possible to separate the frontend (Haskell to Core) and backend
(Core to machine code) from the Haskell compilers (requiring a standard Core
language?)
I'm not sure how many extensions required a change to the Core language.
Most likely this is nice in theory but hard in practice?
On Sun, Feb 22, 2009 at 3:25 PM, John A. De Goes
Is there any conceivable factoring of GHC that would allow you to sandwich the core of jhc in between the front and back ends of GHC? Or are the architectures so fundamentally incompatible as to make this impossible?
Such a factoring would be one way the community could help, and if successful, it would allow you to better focus on the really important stuff.
Regards,
John A. De Goes N-BRAIN, Inc. The Evolution of Collaboration
http://www.n-brain.net | 877-376-2724 x 101
On Feb 20, 2009, at 4:14 PM, John Meacham wrote:
On Fri, Feb 20, 2009 at 11:52:27PM +0100, Thomas Davie wrote:
On 20 Feb 2009, at 23:44, Bulat Ziganshin wrote:
Hello John,
Saturday, February 21, 2009, 1:33:12 AM, you wrote:
Don't forget jhc:
i was pretty sure that jhc will be as fast as gcc :) unfortunately, jhc isn't our production compiler
Why not? There's nothing stopping you from choosing any Haskell compiler you like. If jhc gives you the performance you need – use it.
Heh. He probably meant something more like "jhc is not a production compiler" which is true for a lot of projects. For projects of substantial size or that require many extensions, jhc falls somewhat short. It is getting better though. Of course, help is always appreciated. :)
John
-- John Meacham - ⑆repetae.net⑆john⑈ _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe