GHC and linker choice

Niklas Hambüchen writes: > I have some suggestions for low hanging fruits in this effort. > > 1. Make ghc print more statistics on what it spending time on > > When I did the linking investigation recently >

Re: [ANNOUNCE] GHC 8.2.1 release candidate 1

Hi Ben, it sounds like some of the remaining limitations around DWARF support (e.g. finishing the stack sampling work, local bindings in GDB, ...) could make for a good Haskell Summer of Code project. Have you considered writing this up as one or two project ideas here:

Re: [ANNOUNCE] GHC 8.2.1 release candidate 1

> > * Compiler performance: do you have any numbers to quantify what 8.0 vs 8.2 > > is likely to look like? > > I'm afraid the best I can provide at the moment is [1]. On closer > inspection of these I'm a bit suspicious of the 8.0 numbers; I'll try to > reproduce them (and characterize the

Re: [ANNOUNCE] GHC 8.2.1 release candidate 1

Hi Ben, thank you for this summary. The DWARF status page is helpful. Something was unclear to me though. There are three main potential use cases for DWARF that I see: 1. debugging, possibly with gdb 2. stack traces on exceptions 3. stack sampling, which is a form of performance profiling.

Re: [ANNOUNCE] GHC 8.2.1 release candidate 1

"Boespflug, Mathieu" writes: > Hi Ben, > > this is great news! I'm particularly keen on learning more about two points > you mentioned in your email: > > * Compiler performance: do you have any numbers to quantify what 8.0 vs 8.2 > is likely to look like? I'm afraid the best I

Re: Where do I start if I would like help improve GHC compilation times?

Hey all, thanks a ton for the invaluable pointers. I’m now in the “I-dunno-what-I-am-doing” mode banging SCC annotations like there is no tomorrow, trying to spot any chance for some low-hanging-fruit algorithmic improvement (like using a sequence instead of a list, etc), and will come back to

Re: [ANNOUNCE] GHC 8.2.1 release candidate 1

Phyx writes: > Hi Ben, > > The windows build is unusable. The settings file has $TopDir expanded and > hard-coded to the build path on drydock. > Hmm, this is very odd and sounds like a build system bug since I used the same scripts as usual to generate this bindist. I'll

Re: [ANNOUNCE] GHC 8.2.1 release candidate 1

Hi Ben, The windows build is unusable. The settings file has $TopDir expanded and hard-coded to the build path on drydock. Tamar On Mon, 10 Apr 2017, 08:14 Boespflug, Mathieu, wrote: > Hi Ben, > > this is great news! I'm particularly keen on learning more about two > points you

Re: [ANNOUNCE] GHC 8.2.1 release candidate 1

Hi Ben, this is great news! I'm particularly keen on learning more about two points you mentioned in your email: * Compiler performance: do you have any numbers to quantify what 8.0 vs 8.2 is likely to look like? How much has the work that's been done affect performance across the board? Or are