- ghc-devs - Haskell.org

ghc.haskell.org down! EOM
by Edward Z. Yang 06 Sep '13

06 Sep '13

2 2

Making sure Cabal-1.18.0.1 makes it into GHC 7.8
by Johan Tibell 06 Sep '13

06 Sep '13

Hi, We plan to make a bugfix release of Cabal-1.18 timed such that GHC 7.8 ships with that version. What's the cut-off date for new package versions for the 7.8 release? -- Johan

1 0

A bug of multicore IO manager
by Kazu Yamamoto 05 Sep '13

05 Sep '13

Hi, As I said before, I started running HTTP server using Mio in the real world. Unfortunately, the daemon is not stable. After one day or so, the server cannot accept any HTTP requests. No error messages from the server. The server is alive. To terminate the server (running in a "screen" terminal), single Ctrl-c is not enough. Typing Ctrl-c again terminates the server. After several tests, I'm getting convinced that this occurs only when +RTS -N<x> is specified (where <x> >= 2). The server runs well if +RTS -N<x> is not specified. My question: if the program complied with GHC needs double Ctrl-c to terminate, what is the situation of the program? P.S. It seems to me that the server also is leaking space. The server is getting fatter gradually. --Kazu

5 9

Re: [GHC] #7684: cgrun071 segfaults
by Muhaimin Ahsan 05 Sep '13

05 Sep '13

Here's the dumped asm: http://ghc.haskell.org/trac/ghc/attachment/ticket/7684/cgrun071.S Muhaimin Ahsan On Sep 5, 2013, at 12:06 PM, "GHC" <ghc-devs(a)haskell.org> wrote: > #7684: cgrun071 segfaults > ----------------------------------+---------------------------------- > Reporter: tibbe | Owner: leroux > Type: bug | Status: new > Priority: normal | Milestone: 7.8.1 > Component: Compiler | Version: 7.7 > Resolution: | Keywords: > Operating System: MacOS X | Architecture: x86_64 (amd64) > Type of failure: Runtime crash | Difficulty: Unknown > Test Case: cgrun071 | Blocked By: > Blocking: | Related Tickets: > ----------------------------------+---------------------------------- > > Comment (by tibbe): > > I'm confused. The test isn't compiled with -msse42 and thus the popcnt > instruction should never be omitted (check the output assembly to make > sure) so it seems more likely that the failure has to do with narrowing. > > -- > Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/7684#comment:20> > GHC <http://www.haskell.org/ghc/> > The Glasgow Haskell Compiler

2 1

Re: [GHC] #7684: cgrun071 segfaults
by Johan Tibell 05 Sep '13

05 Sep '13

I don't think we should. We should either call the C based fallback implementation in the ghc-prim package or the popcnt instruction. The Haskell implementation in the test is a toy that should only be used to validate that the primop computes the right result. If the instruction is being incorrectly used when it's not available we should fix that. On Thu, Sep 5, 2013 at 9:47 AM, Muhaimin Ahsan <leroux(a)fezrev.com> wrote: > I'm asking if we should call it in the real implementation of the PrimOp. This isn't a problem across all platforms; it's specific to apple-gcc42, I believe based on yesterday's findings. I'll continue working on it later today. Also, I'm extremely new to GHC internals (this is the second bug I'm tackling), so I may be viewing things the wrong and would appreciate pointers. > > Muhaimin Ahsan > > On Sep 5, 2013, at 9:09 AM, Johan Tibell <johan.tibell(a)gmail.com> wrote: > >> On Thu, Sep 5, 2013 at 12:20 AM, GHC <ghc-devs(a)haskell.org> wrote: >>> Should we switch to calling the "slower" popCount for this certain case? >>> https://github.com/ghc/testsuite/blob/master/tests/codeGen/should_run/cgrun… >>> {{{ >>> slowPopcnt :: Word -> Word >>> slowPopcnt x = count' (bitSize x) x 0 >>> where >>> count' 0 _ !acc = acc >>> count' n x acc = count' (n-1) (x `shiftR` 1) >>> (acc + if x .&. 1 == 1 then 1 else 0) >>> }}} >> >> I've not been following this closely so apologies if I've >> misunderstood the issue. >> >> Are you asking if we should call slowPopcnt in the test in more >> circumstances or if we should call it in the real implementation of >> the primop? The primop already has a fallback if the popcnt >> instruction isn't available (it uses a table-based implementation). >> >> _______________________________________________ >> ghc-devs mailing list >> ghc-devs(a)haskell.org >> http://www.haskell.org/mailman/listinfo/ghc-devs >

1 0

Re: [GHC] #7684: cgrun071 segfaults
by Johan Tibell 05 Sep '13

05 Sep '13

On Thu, Sep 5, 2013 at 12:20 AM, GHC <ghc-devs(a)haskell.org> wrote: > Should we switch to calling the "slower" popCount for this certain case? > https://github.com/ghc/testsuite/blob/master/tests/codeGen/should_run/cgrun… > {{{ > slowPopcnt :: Word -> Word > slowPopcnt x = count' (bitSize x) x 0 > where > count' 0 _ !acc = acc > count' n x acc = count' (n-1) (x `shiftR` 1) > (acc + if x .&. 1 == 1 then 1 else 0) > }}} I've not been following this closely so apologies if I've misunderstood the issue. Are you asking if we should call slowPopcnt in the test in more circumstances or if we should call it in the real implementation of the primop? The primop already has a fallback if the popcnt instruction isn't available (it uses a table-based implementation).

1 0

RE: GHC 7.8 release status
by Simon Peyton-Jones 05 Sep '13

05 Sep '13

Maybe not, but you'll have to move fast. · Make a branch (Iavor can do that) · Update the wiki page describing the design: http://ghc.haskell.org/trac/ghc/wiki/GhcKinds/KindsWithoutData You can demote any design alternatives that you discarded, putting them in an appendix at the end. · Update documentation in the user manual · Make sure you have tests in the testsuite How fast can you do that? Simon From: Trevor Elliott [mailto:awesomelyawesome@gmail.com] Sent: 04 September 2013 18:30 To: Iavor Diatchki; Simon Peyton-Jones Subject: Re: GHC 7.8 release status Hi Simon, We had talked during your Galois visit about the changes that Iavor and I had made to -XDataKinds, allowing different syntax when introducing a new kind. Have we missed the window to make it into the 7.8 release? Thanks! --trevor On Wed, Sep 4, 2013 at 10:27 AM, Iavor Diatchki <iavor.diatchki(a)gmail.com<mailto:iavor.diatchki@gmail.com>> wrote: ---------- Forwarded message ---------- From: Simon Peyton-Jones <simonpj(a)microsoft.com<mailto:simonpj@microsoft.com>> Date: Wed, Sep 4, 2013 at 6:52 AM Subject: GHC 7.8 release status To: Nicolas Frisby <nicolas.frisby(a)gmail.com<mailto:nicolas.frisby@gmail.com>>, "Pedro Magalhães (dreixel(a)gmail.com<mailto:dreixel@gmail.com>)" <dreixel(a)gmail.com<mailto:dreixel@gmail.com>>, "Richard Eisenberg (eir(a)cis.upenn.edu<mailto:eir@cis.upenn.edu>)" <eir(a)cis.upenn.edu<mailto:eir@cis.upenn.edu>>, "Geoffrey Mainland (mainland(a)cs.drexel.edu<mailto:mainland@cs.drexel.edu>)" <mainland(a)cs.drexel.edu<mailto:mainland@cs.drexel.edu>>, Iavor Diatchki <iavor.diatchki(a)gmail.com<mailto:iavor.diatchki@gmail.com>>, Austin Seipp <aseipp(a)pobox.com<mailto:aseipp@pobox.com>>, Edsko de Vries <edsko(a)well-typed.com<mailto:edsko@well-typed.com>>, "Ryan Newton (rrnewton(a)gmail.com<mailto:rrnewton@gmail.com>)" <rrnewton(a)gmail.com<mailto:rrnewton@gmail.com>>, Luite Stegeman <stegeman(a)gmail.com<mailto:stegeman@gmail.com>>, Thomas Schilling <nominolo(a)googlemail.com<mailto:nominolo@googlemail.com>>, David Luposchainsky <dluposchainsky(a)googlemail.com<mailto:dluposchainsky@googlemail.com>> Cc: "ghc-devs(a)haskell.org<mailto:ghc-devs@haskell.org>" <ghc-devs(a)haskell.org<mailto:ghc-devs@haskell.org>> Friends The 7.8 release is imminent. This email is to ask abou the status of your contributions. In each case could you update the wiki with the current state of play, and your intentions, including dates. That is, don't put your reply in email: it on the status page below; though by all means send email too! Summary here: http://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.8 Also : What is missing from the list that should be done? * Patrick Palka: status of ghc -make -j? * Nick: status of your three items? * Pedro/Richard: is all the Typeable stuff, and gcast and friends, finished? * Geoff: what about the new Template Haskell story? * Iavor: when do you think you can merge? * Austin: what about ARMv7? * Edsko/Thomas/Luite: if you want anything for 7.8 it'll have to be jolly soon. At the moment I don't even know the motivation or design, let alone implementation. Could you make a wiki page explaining the proposed design? Is it really important to do this for 7.8? * Dynamic GHCi. I have no idea who is driving this, or how important it is. * Ryan: atomic stuff. All merged? * AMP warnings: David Luposchainsky is driving this. Thanks! Simon Microsoft Research Limited (company number 03369488) is registered in England and Wales Registered office is at 21 Station Road, Cambridge, CB1 2FB

1 0

Haskeline 0.7.0.4
by Edward Z. Yang 05 Sep '13

05 Sep '13

Hey Judah, We're gearing up for another GHC release, and there a small number of patches which are still in GHC's tree which have not made it into the upstream haskeline repository: commit 495b00b4f125c0b4e7f1e966cd961eae89cffdc0 Author: Herbert Valerio Riedel <hvr(a)gnu.org> Date: Sat Aug 31 10:31:52 2013 +0200 Avoid shadowing `handlers` variable in `catches` commit 40bcd6ac30577d1d240166674d1e328ac52c1fd5 Author: Ian Lynagh <ian(a)well-typed.com> Date: Tue Jul 2 16:46:53 2013 +0100 Fix build on Win64 commit 3a92ddd63d4edc622ad4af044c5b664aa64c3dd4 Author: Ian Lynagh <ian(a)well-typed.com> Date: Sun Feb 17 20:25:10 2013 +0000 Follow unix's version bump Additionally, I have one more patch for the Windows build, attached below: commit 80f2fafe39cbc86205afb2eac8d4f60a1ce2684e Author: Edward Z. Yang <ezyang(a)mit.edu> Date: Wed Sep 4 17:45:37 2013 -0700 Avoid Handler identifier conflict in Windows. Signed-off-by: Edward Z. Yang <ezyang(a)mit.edu> diff --git a/System/Console/Haskeline/Backend/Win32.hsc b/System/Console/Haskeline/Backend/Win32.hsc index d54df2c..4447519 100644 --- a/System/Console/Haskeline/Backend/Win32.hsc +++ b/System/Console/Haskeline/Backend/Win32.hsc @@ -17,7 +17,7 @@ import Data.Maybe(mapMaybe) import Control.Monad import System.Console.Haskeline.Key -import System.Console.Haskeline.Monads +import System.Console.Haskeline.Monads hiding (Handler) import System.Console.Haskeline.LineState import System.Console.Haskeline.Term import System.Console.Haskeline.Backend.WCWidth Thanks, Edward

2 2

Status of Windows validate
by Edward Z. Yang 05 Sep '13

05 Sep '13

A lot of failures: ---- Unexpected results from: TEST="T5313 registry001 cabal01 dynamicToo002 dynHelloWorld T1969 T5030 T3294 T7797 T7850 haddock.Cabal haddock.compiler haddock.base linker_unload derefnull T4850 divbyzero T8172 ghci058 prog002 prog003 ImpSafeOnly08 safePkg01 ImpSafeOnly02 ImpSafeOnly03 ImpSafeOnly01 ImpSafeOnly06 ImpSafeOnly07 ImpSafeOnly04 ImpSafeOnly05 ImpSafeOnly09 ImpSafeOnly10" OVERALL SUMMARY for test run started at now 3724 total tests, which gave rise to 12242 test cases, of which 8869 were skipped 27 had missing libraries 3248 expected passes 61 expected failures 18 caused framework failures 1 unexpected passes 31 unexpected failures Unexpected passes: driver T5313 (normal) Unexpected failures: ../../libraries/Win32/tests registry001 [bad exit code] (normal) cabal/cabal01 cabal01 [bad exit code] (normal) driver dynHelloWorld [bad exit code] (dyn) driver/dynamicToo/dynamicToo002 dynamicToo002 [bad stdout] (normal) ghci/prog002 prog002 [bad exit code] (ghci) ghci/prog003 prog003 [bad exit code] (ghci) ghci/scripts T8172 [bad stdout] (ghci) ghci/scripts ghci058 [bad exit code] (ghci) perf/compiler T1969 [stat not good enough] (normal) perf/compiler T5030 [stat too good] (normal) perf/haddock haddock.Cabal [stat not good enough] (normal) perf/haddock haddock.base [stat not good enough] (normal) perf/haddock haddock.compiler [stat too good] (normal) perf/should_run T7797 [stat too good] (normal) perf/should_run T7850 [stat too good] (normal) rts T4850 [bad stdout] (normal) rts derefnull [bad exit code] (normal) rts divbyzero [bad exit code] (normal) rts linker_unload [bad exit code] (normal) safeHaskell/check/pkg01 ImpSafeOnly01 [exit code non-0] (normal) safeHaskell/check/pkg01 ImpSafeOnly02 [exit code non-0] (normal) safeHaskell/check/pkg01 ImpSafeOnly03 [stderr mismatch] (normal) safeHaskell/check/pkg01 ImpSafeOnly04 [exit code non-0] (normal) safeHaskell/check/pkg01 ImpSafeOnly05 [stderr mismatch] (normal) safeHaskell/check/pkg01 ImpSafeOnly06 [exit code non-0] (normal) safeHaskell/check/pkg01 ImpSafeOnly07 [stderr mismatch] (normal) safeHaskell/check/pkg01 ImpSafeOnly08 [stderr mismatch] (normal) safeHaskell/check/pkg01 ImpSafeOnly09 [stderr mismatch] (normal) safeHaskell/check/pkg01 ImpSafeOnly10 [exit code non-0] (normal) safeHaskell/check/pkg01 safePkg01 [bad exit code] (normal) Cheers, Edward

1 0

Re: RE: More windows woe
by Jost Berthold 05 Sep '13

05 Sep '13

> From: Simon Peyton-Jones <simonpj(a)microsoft.com> > To: "Edward Z. Yang" <ezyang(a)MIT.EDU>, Simon Marlow > <marlowsd(a)gmail.com> > Cc: "ghc-devs(a)haskell.org" <ghc-devs(a)haskell.org> > Subject: RE: More windows woe > Message-ID: > <59543203684B2244980D7E4057D5FBC1485BB7AB(a)DB3EX14MBXC308.europe.corp.microsoft.com> > > Content-Type: text/plain; charset="utf-8" > > Simon Marlow: please help! > At the moment windows builds are hosed, which is a Bad Situation. > > Actually it turns out that what want is > > debugBelch("Checking whether to unload %S\n", oc->fileName)); > > That is, use "%S" rather than "%s" as format specifier for wide chars. > > Sadly, this works on Windows, but not on Linux: > rts/CheckUnload.c:260:13: > error: format ?%S? expects argument of type ?wchar_t *?, but argument 2 has type ?pathchar *? [-Werror=format] > > > So what I need guidance on, please!, is what the approved way to deal with this is. I suppose that I could identify each use of %s on a filepath and say > > #ifdef mingw32_HOST_OS > debugBelch("Checking whether to unload %S\n", oc->fileName)); > #else > debugBelch("Checking whether to unload %s\n", oc->fileName)); > #endif > > But that seems deeply unsatisfactory doesn't it? > > If not that, then what? > > > Simon Similar code is in place to distinguish between 32-bit and 64-bit StgWords: > grep -r -e FMT_Word includes/ includes/stg/Types.h:#define FMT_Word32 "u" includes/stg/Types.h:#define FMT_Word32 "lu" includes/stg/Types.h:#define FMT_Word64 "lu" includes/stg/Types.h:#define FMT_Word64 "llu" includes/stg/Types.h:#define FMT_Word FMT_Word64 includes/stg/Types.h:#define FMT_Word FMT_Word32 and format strings like "blabla " FMT_Word " ..blabla" are used inside rts/. One could do the same for FMT_Path and introduce it where required. Maybe this would be acceptable? / Jost

4 6