| As you may have noticed, I have finally pushed a large number of patches | for the new code generator. The new codegen is still off by default, so
Brilliant thank you. I'll validate myself now. How's your defence preparation going? What's the flag to switch on the new path? I'll look forward to the day when you say "it can be on by default", so we can delete all the old code! Worth doing some simple compile-time tests (use nofib) to see if compile times increase when using the new path. best wishes Simon | -----Original Message----- | From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Dias | Sent: 26 November 2008 05:32 | To: [email protected] | Subject: new codegen patches | | As you may have noticed, I have finally pushed a large number of patches | for the new code generator. The new codegen is still off by default, so | for the most part, this patch should not have any effect on compiled | programs. I validated the patches, but please let me know if there are any | problems. | | In case you're wondering about the status of the new code generator: There | are still bugs that show up with the stage2 build, although the regression | testsuite and nofib testsuite work with the stage1 build. Hopefully, I'll | have some more patches soon. | | Thanks, | John | | _______________________________________________ | Cvs-ghc mailing list | [email protected] | http://www.haskell.org/mailman/listinfo/cvs-ghc _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
