Re: RFC: Removing the `-hb` profiling option

2016-05-06 Thread Bardur Arantsson
On 05/06/2016 11:04 AM, Erik de Castro Lopo wrote: > Hi all, > > After a bit of rather tedious and frustrating debugging I came to the > realisation that the code for the `-hb` profiling option is not thread > safe. See https://ghc.haskell.org/trac/ghc/ticket/12019 > > This gives us an

Re: RFC: Removing the `-hb` profiling option

2016-05-06 Thread davean
On Fri, May 6, 2016 at 1:39 PM, Carter Schonwald wrote: > What about disallowing -hb on threaded builds? That does just sort of punt > it a little bit, it a not quite satisfactory way perhaps But the non-threaded runtime isn't really a first class citizen, is it?

Re: RFC: Removing the `-hb` profiling option

2016-05-06 Thread Carter Schonwald
What about disallowing -hb on threaded builds? That does just sort of punt it a little bit, it a not quite satisfactory way perhaps On Friday, May 6, 2016, Evan Laforge wrote: > I've used this a lot when looking for leaks. Especially combined with > other things like -hbdrag

Re: RFC: Removing the `-hb` profiling option

2016-05-06 Thread Evan Laforge
I've used this a lot when looking for leaks. Especially combined with other things like -hbdrag -hc, so I'd be sad to see it go. Without it, how do you find lag and drag? On the other hand, the entire profiling system has been hard to use because of crashes (perhaps due to that thread-unsafety

Re: RFC: Removing the `-hb` profiling option

2016-05-06 Thread Iavor Diatchki
I think that biographical profiling is quite nice! I wouldn't say that it is *more* useful than other modes of profiling, but it is certainly complementary, and helps give you an idea of what's going on. So I'd very much vote for fixing it rather than removing it. -Iavor On Fri, May 6, 2016 at

RFC: Removing the `-hb` profiling option

2016-05-06 Thread Erik de Castro Lopo
Hi all, After a bit of rather tedious and frustrating debugging I came to the realisation that the code for the `-hb` profiling option is not thread safe. See https://ghc.haskell.org/trac/ghc/ticket/12019 This gives us an opportunity to simply remove it instead of fixing it. If there is anyone