Linker reorganization

Hello RTS people, Today I finally grew frustrated enough with my constant battle with the 7000 line tangle of CPP that is rts/Linker.c to do something about it. The result is D2643 through D2650. In short, I took the file and chopped it into more managable pieces: * linker/PEi386.[ch]: PE

Specialization plugin

Hi everyone, I'm trying my hand at writing a GHC plugin to generate specializations for all uses of a particular typeclass, and I've run into some trouble. I'd appreciate it if someone could point me in the right direction! I'm new to GHC development, so I may just be overlooking some simple

Dynamic Linking help

Hi *, I’ve been working the past 4 or so months on reviving dynamic linking support for Windows in a way that has the most chance of working. My first patch in the series is up on Phabricator and with this patch dynamic linking work again, but only for the threaded RTS. The reason for this is

Re: setnumcapabilities001 failure

Briefly looking at the code it seems like several global variables involved should be volatile: n_capabilities, enabled_capabilities, and capabilities. Perhaps in a loop like in scheduleDoGC the compiler moves the reads of n_capabilites or capabilites outside the loop. A failed requestSync in

Re: setnumcapabilities001 failure

Simon Marlow writes: > I haven't been able to reproduce the failure yet. :( > Indeed I've also not seen it in my own local builds. It's quite an fragile failure. Cheers, - Ben signature.asc Description: PGP signature ___

Re: setnumcapabilities001 failure

Simon Marlow writes: > How many cores does the builder machine have? (this should make it easier > for me to repro) > It looks like 8. Cheers, - Ben signature.asc Description: PGP signature ___ ghc-devs mailing list

Re: OSX failing

Matthew Pickering writes: > I will revert the commit which caused the build failure as I am not > able to fix it myself. It is hard to get this stuff right as > differentials are not built on OSX. > Thanks Matthew. I'll try to clean this up. Cheers, - Ben

Re: How to best display type variables with the same name

On 26 October 2016 at 11:43, Simon Peyton Jones wrote: > As far as I understand it: > > · You are plucking a type from the midst of a syntax tree, and > displaying it. > > · That type might well mention type variables that are bound > “further out” > > o

OSX failing

All OSX builds are failing with rts/Linker.c:6371:1: error: error: unused function 'machoGetMisalignment' [-Werror,-Wunused-function] See eg https://phabricator.haskell.org/harbormaster/build/14551/ So I get lots of “Phab failed” messages, and am now simply deleting them, which rather defeats