Aside: cabal supports hpc and puts the various files (e.g. .tix) in separate directories to avoid problems like these.
On Thu, Nov 7, 2013 at 8:55 AM, Roman Cheplyaka <r...@ro-che.info> wrote: > So Evan's prediction was accurate ;-) > > * Carter Schonwald <carter.schonw...@gmail.com> [2013-11-07 00:29:24-0500] > > Evan, > > > > if you want to get involved in working on HPC, go for it! theres many > many > > pieces of ghc that need more proactive ownership. > > > > i should probably use HPC a bit as i start getting my numerical libs out, > > and i'm sure future me will appreciate current you working on making it > > better > > > > -Carter > > > > > > On Thu, Nov 7, 2013 at 12:03 AM, Evan Laforge <qdun...@gmail.com> wrote: > > > > > Is anyone out there using HPC? It seems like it was gotten into a > > > more or less working if not ideal state, and then abandoned. > > > > > > Things I've noticed lately: > > > > > > The GHC runtime just quits on the spot if there's already a tix file. > > > This bit me when I was parallelizing tests. It's also completely > > > unsafe when run concurrently, mostly it just overwrites the file, > > > sometimes it quits. Sure to cause headaches for someone trying to > > > parallelize tests. > > > > > > You can't change the name of the output tix file, so I worked around > > > by hardlinking the binary to a bunch of new ones, and then doing 'hpc > > > sum' on the results. > > > > > > The hpc command is super slow. It might have to do with it doing its > > > parsing with Prelude's 'read', and it certainly doesn't help the error > > > msgs. > > > > > > And the whole thing is generally minimally documented. > > > > > > I can already predict the answer will be "yes, HPC could use some > > > love, roll up your sleeves and welcome!" It does look like it could > > > be improved a lot with just a bit of effort, but that would be a yak > > > too far for me, at the moment. I'm presently just curious if anyone > > > else out there is using it, and if they feel like it could do with a > > > bit of polishing. > > > _______________________________________________ > > > Glasgow-haskell-users mailing list > > > Glasgow-haskell-users@haskell.org > > > http://www.haskell.org/mailman/listinfo/glasgow-haskell-users > > > > > > _______________________________________________ > > Glasgow-haskell-users mailing list > > Glasgow-haskell-users@haskell.org > > http://www.haskell.org/mailman/listinfo/glasgow-haskell-users > > > _______________________________________________ > Glasgow-haskell-users mailing list > Glasgow-haskell-users@haskell.org > http://www.haskell.org/mailman/listinfo/glasgow-haskell-users > >
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users