Yeah, it's not like a big deal or anything. Here's all the places which
grep told me use chains of || (or long switch statements which can't be
turned into tables) to compare these values:
ghc/rts//win32/AsyncIO.c:280
ghc/rts//Threads.c:286
ghc/rts//Threads.c:257
ghc/rts//sm/Scav.c:73
ghc/rts//sm/
I'm afraid so - I am just creating the ticket.
/ jost
On 07/19/2014 09:07 PM, Carter Schonwald wrote:
Wait, does that mean the corresponding constants in base for 7.8.3 are
busted?
On Saturday, July 19, 2014, Jost Berthold
mailto:berth...@mathematik.uni-marburg.de>> wrote:
Message: 2
Wait, does that mean the corresponding constants in base for 7.8.3 are
busted?
On Saturday, July 19, 2014, Jost Berthold <
berth...@mathematik.uni-marburg.de> wrote:
> Message: 2
>> Date: Sat, 19 Jul 2014 15:00:17 +1000
>> From: Kyle Van Berendonck
>> To: "ghc-devs@haskell.org"
>> Subject: Thre
Message: 2
Date: Sat, 19 Jul 2014 15:00:17 +1000
From: Kyle Van Berendonck
To: "ghc-devs@haskell.org"
Subject: Thread status constants
Message-ID:
Content-Type: text/plain; charset="utf-8"
Hi,
I found these:
https://github.com/ghc/ghc/blob/5f3c5384df59717ca8013c5df8d1f65692867825/incl
Here's my remaining list before putting out a realse candidate. I'm aiming
for this weekend:
*-- General --*
[ ] haddock linkage from HP packages to GHC core packages is broken
[ ] decision on QuickCheck?
*-- Source Tarball --*
[ ] missing platform.sh scripts
[ ] missing os-extras in hptool/src
Hi,
Am Samstag, den 19.07.2014, 01:14 +0100 schrieb Edward Z.Yang:
> The reason for this is that the builders do not have a sufficiently
> recent version of process, which Cabal has upgraded to depend on.
> Probably 'cabal update && cabal install process' should bring it up to
> date and make it w
