| profiling bigtime. I fixed it, but I don't know whether y'all want my code... | (for some reason I feel like I'm talking to myself here.)
Sorry about that. The ICFP deadline was last Friday, and both Simon and I have been largely away since then. And I was away quite a bit during March too. Net result: slow progress on the GHC front and lack of response to ghc-bug mail. Simon is still away early next week, but after that I think we'll be more or less back to normal. More generally, GHC has become large enough, and is used by enough people, that Simon and I are hard pressed to keep up with all the ways people use it. For example, I confess that generating External Core with profiling on, and reading it in again, isn't something that we'd tested. I'm sure this maintenance issue will become increasingly pressing. This is basically good news --- GHC is used by more and more people to do more and more things on more and more platforms. To make it sustainable, though, we need more of you GHC users to be willing to help fix problems. Quite a few people already do (see for example http://haskell.cs.yale.edu/ghc/contributors.html; please yell if you think you should be credited there and aren't) but more are needed. We love it when people send us cures as well as bug reports! GHC's long term future as open-source software relies on participation by as many folk as possible. So Kirsten, yes do please send your proposed patch. Thanks for digging deep enough to find out what's going on. Simon _______________________________________________ Glasgow-haskell-bugs mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
