
Friends The status of the GHC 7.8 release is here https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.8/RC2. Alas we are currently stalled on #8870, #8834: we are getting seg-faults on Windows. (For example, on my laptop, the stage2 compiler seg-faults when compiling some (but not all) files. Although few people develop GHC on Windows, many people *use* GHC on Windows, so we can't really release in this state. We need help! Austin is trying, but it's all working on his Windows build. He's trying to get more machines to see if he can reproduce the failure there. Does anyone feel able to help? Even git-bisecting to find the offending commit would be a huge help. In principle I can do that (at two hours per bisection) but I was defeated by an out-of-sync Haddock. I need to know how to remove Haddock from the build altogether. But others are far more skilled than me. On #8834 Simon M speculates that we may have the callee-saves register wrong on Win64. Does anyone feel up to looking into that? Until we find what's going on, 7.8 is stalled. Thanks! Simon

I can provide help on #8834 because I know what was done in the commit that introduced the bug. But I don't have Windows so I'm afraid we still need someone to do the actual work. Janek Dnia środa, 12 marca 2014, Simon Peyton Jones napisał:
Friends The status of the GHC 7.8 release is here https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.8/RC2. Alas we are currently stalled on #8870, #8834: we are getting seg-faults on Windows. (For example, on my laptop, the stage2 compiler seg-faults when compiling some (but not all) files. Although few people develop GHC on Windows, many people *use* GHC on Windows, so we can't really release in this state. We need help! Austin is trying, but it's all working on his Windows build. He's trying to get more machines to see if he can reproduce the failure there. Does anyone feel able to help? Even git-bisecting to find the offending commit would be a huge help. In principle I can do that (at two hours per bisection) but I was defeated by an out-of-sync Haddock. I need to know how to remove Haddock from the build altogether. But others are far more skilled than me. On #8834 Simon M speculates that we may have the callee-saves register wrong on Win64. Does anyone feel up to looking into that? Until we find what's going on, 7.8 is stalled. Thanks! Simon

On 12.03.2014 19:04, Simon Peyton Jones wrote:
Alas we are currently stalled on #8870, #8834: we are getting seg-faults on Windows. (For example, on my laptop, the stage2 compiler seg-faults when compiling some (but not all) files. Although few people develop GHC on Windows, many people **use** GHC on Windows, so we can’t really release in this state.
We need help! Austin is trying, but it’s all working on his Windows build. He’s trying to get more machines to see if he can reproduce the failure there.
Does anyone feel able to help? Even git-bisecting to find the offending commit would be a huge help.
As I've already wrote in comments to #8834 I can't reproduce #8870 using 32-bit GHC on 64-bit Windows OS. Both of my machines have only 64-bit Windows installed. So no help here, sorry.
On #8834 Simon M speculates that we may have the callee-saves register wrong on Win64. Does anyone feel up to looking into that?
After reading Simon M comment I've looked into win64 documentation and `includes/stg/MachRegs.h` file. Perhaps, I've missed something, but I've seen nothing wrong there, `includes/stg/MachRegs.h` is even a bit too conservative regarding windows. I probably could help, but this would require a lot of learning of Cmm-related things (I've made reverting patch completely mechanically), so I'd want to know that nobody else would work on this. Sorry for strange empty messages from me. Something wrong happened with my Thunderbird. Regards, Kyra

| conservative regarding windows. I probably could help, but this would | require a lot of learning of Cmm-related things (I've made reverting | patch completely mechanically), so I'd want to know that nobody else | would work on this. Just trying to reproduce the crash, and then git-bisecting to the fault, would be a huge step forward. I don't think you'd need to know Cmm necessarily Simon | -----Original Message----- | From: ghc-devs [mailto:ghc-devs-bounces@haskell.org] On Behalf Of Kyra | Sent: 12 March 2014 15:36 | To: ghc-devs@haskell.org | Subject: Re: GHC 7.8 release | | On 12.03.2014 19:04, Simon Peyton Jones wrote: | > Alas we are currently stalled on #8870, #8834: we are getting | > seg-faults on Windows. (For example, on my laptop, the stage2 compiler | > seg-faults when compiling some (but not all) files. Although few | > people develop GHC on Windows, many people **use** GHC on Windows, so | > we can't really release in this state. | > | > We need help! Austin is trying, but it's all working on his Windows | > build. He's trying to get more machines to see if he can reproduce the | > failure there. | > | > Does anyone feel able to help? Even git-bisecting to find the | > offending commit would be a huge help. | > | As I've already wrote in comments to #8834 I can't reproduce #8870 using | 32-bit GHC on 64-bit Windows OS. Both of my machines have only 64-bit | Windows installed. So no help here, sorry. | > | > On #8834 Simon M speculates that we may have the callee-saves register | > wrong on Win64. Does anyone feel up to looking into that? | > | After reading Simon M comment I've looked into win64 documentation and | `includes/stg/MachRegs.h` file. Perhaps, I've missed something, but I've | seen nothing wrong there, `includes/stg/MachRegs.h` is even a bit too | conservative regarding windows. I probably could help, but this would | require a lot of learning of Cmm-related things (I've made reverting | patch completely mechanically), so I'd want to know that nobody else | would work on this. | | Sorry for strange empty messages from me. Something wrong happened with | my Thunderbird. | | Regards, | Kyra | _______________________________________________ | ghc-devs mailing list | ghc-devs@haskell.org | http://www.haskell.org/mailman/listinfo/ghc-devs

On 12/03/14 15:04, Simon Peyton Jones wrote:
Friends The status of the GHC 7.8 release is here https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.8/RC2. Alas we are currently stalled on #8870, #8834: we are getting seg-faults on Windows. (For example, on my laptop, the stage2 compiler seg-faults when compiling some (but not all) files. Although few people develop GHC on Windows, many people *use* GHC on Windows, so we can't really release in this state. We need help! Austin is trying, but it's all working on his Windows build. He's trying to get more machines to see if he can reproduce the failure there. Does anyone feel able to help? Even git-bisecting to find the offending commit would be a huge help. In principle I can do that (at two hours per bisection) but I was defeated by an out-of-sync Haddock. I need to know how to remove Haddock from the build altogether. But others are far more skilled than me.
Assuming Haddock is not the thing causing the problems here, I think it wouldn't be unreasonable to simply replace all contents of the Haddock directory with some dummy Main file, ask GHC to not build with docs and to not run any of the Haddock tests. This will only work if GHC doesn't use any of the exposed Haddock API of course. I believe I heard someone in #ghc say that Haddock is not a proper submodule of the repository (why isn't it?) so that's probably why it's going out of sync. We even have a long outstanding bug on Haddock Trac because we have no idea how to sanely bisect Haddock and GHC together to find the change!
On #8834 Simon M speculates that we may have the callee-saves register wrong on Win64. Does anyone feel up to looking into that? Until we find what's going on, 7.8 is stalled. Thanks! Simon
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
-- Mateusz K.
participants (4)
-
Jan Stolarek
-
Kyra
-
Mateusz Kowalczyk
-
Simon Peyton Jones