I wrote a ghc-server that starts a persistent process for each cpu. Then a 'ghc' frontend wrapper sticks each job in a queue. It seemed to be working, but timing tests didn't reveal any speed-up. Then I got a faster computer and lost motivation. I didn't investigate very deeply why it didn't speed up as I hoped. It's possible the approach is still valid, but I made some mistake in the implementation.
So I can stop writing this little blurb I put it on github: https://github.com/elaforge/ghc-server On Mon, May 13, 2013 at 8:40 PM, Niklas Hambüchen <m...@nh2.me> wrote: > I know this has been talked about before and also a bit in the recent > GSoC discussion. > > I would like to know what prevents ghc --make from working in parallel, > who worked at that in the past, what their findings were and a general > estimation of the difficulty of the problem. > > Afterwards, I would update > http://hackage.haskell.org/trac/ghc/ticket/910 with a short summary of > what the current situation is. > > Thanks to those who know more! > > _______________________________________________ > 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