Hi Am Mittwoch, den 20.09.2017, 14:33 -0400 schrieb Ben Gamari: > Note that valgrind can also do cache modelling so I suspect it can give > you a reasonably good picture of execution; certainly better than > runtime. However, the trade-off is that (last I checked) it's incredibly > slow. Don't you think I mean just a bit less peppy than usual. I mean > soul-crushingly, mollasses-on-a-cold-December-morning slow. > > If we think that we can bear the cost of running valigrind then I think > it would be a great improvement. As you point out, the current run times > are essentially useless.
I did it for my thesis and I found it ok. I mean I always sent it off to some machine and looked at the results later, so I did not really care whether it took 30mins or 2h. I think I’ll try it in perf.haskell.org and see what happens. Joachim -- Joachim “nomeata” Breitner m...@joachim-breitner.de https://www.joachim-breitner.de/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs