Hi all, One final update: I have found a workaround for the issue Mateusz reported last week. Luckily it can be fought off somewhat easily for now for OS X users, but there are more details here: https://github.com/haskell/cabal/issues/1740 The final thing that ended up being a hold-up is now #8870 - the 32bit Windows distribution is segfaulting. At first, I thought this was an anomaly, but I saw several other people who also reported this problem. After a bit of sweat I've finally reproduced this bug and tracked this down part of the way, but I've been especially confused by this issue because apparently it does not affect everyone! Which is quite bizarre, as given the results I found, I'd suspect everyone to see it. Right now, Kyrill has suggested a fix I'm attempting (I slightly botched my first try), and I have found a way to avoid it at the moment by turning off optimization (which seems to reduce stack pressure enough to get by on Windows - see the ticket for details). Are there any Windows users who would be willing to test a 32bit Windows binary distribution, should I make a provisional one? I can have it up within a few hours from now. I'd really love some outside confirmation of this problem and a resolution once we have it! As this is the last bug, if I can at least get some confirmation a fix works, I can have the final release out immediately afterwords - the tree is otherwise quiet and will remain so. On Tue, Mar 25, 2014 at 5:24 PM, Austin Seipp <austin@well-typed.com> wrote:
Hello all,
As an updated, I'm looking into the report Mateusz had of 'free' failing to build haddocks on OS X*, which I've reproduced. It seems nasty - I'll follow up with details ASAP.
* See his recent email to ghc-devs about this problem.
On Tue, Mar 25, 2014 at 12:11 PM, Mateusz Kowalczyk <fuuzetsu@fuuzetsu.co.uk> wrote:
On 25/03/14 17:09, kyra wrote:
On 3/25/2014 20:52, Mateusz Kowalczyk wrote:
The only instances of Haddock becoming really slow that I can think of is some rather old ticket (#101 on Haddock Trac) in presence of Template Haskell but I have closed it a while ago due to lack of information to go on and inability to replicate without the reporter's help. Perhaps this was your use case?
Aha, this is why I could not reproduce it! I checked it on packages which used no TH, and that slow behaviour occurred when TH was involved!
I think it is TH which really triggers producing and splitting of an assembly output and in this case no-splitting gives *huge* benefit. Sadly, I have no time to check this right now.
Regards, Kyra
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
There's no rush as it's not going to get into 7.8.1 anyway but I would love to see some numbers before 7.8.2 so please keep us in mind.
Thanks!
-- Mateusz K. _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
-- Regards,
Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/
-- Regards, Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/