I think that the preprocessor is going to be a major impediment to getting GHC compiling with clang. If we had a Haskell-specific preprocessor that would be a big help, but it seems to me that it could be a lot of work to get it just right.
Also, the preprocossor is use for cmm files which might cause even more problems. For example, the clang preprocessor was printing .. as . . which caused problems in cmm range expressions. I submitted a patch to fix this, but there are probably other issues to trip us up. The overall position of the clang developers were that they didn't have much sympathy for people using a C preprocessor on non-C languages. On Jun 29, 2011, at 2:38 AM, Max Bolingbroke wrote: > On 29 June 2011 06:46, Dan Knapp <[email protected]> wrote: >> That sounds a lot easier than doing a preprocessor from scratch, so > > I would quite like a Haskell-specific preprocessor because the current > GCC CPP even has problems if you use identifiers containing single ' > characters within macros. So this use of an ASSERT macro will fail > obscurely: > > ASSERT(isFooBar x', ppr x') > > It's kind of annoying to have to rename your identifiers when this happens. > > Max > > _______________________________________________ > 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
