- ghc-devs - Haskell.org

Time files... and here's another alpha HP for 7.10
by Mark Lentczner 10 Jun '15

10 Jun '15

So - I hear from a bird that 7.10.2 might be just around the corner. I'm getting ahead of the curve! I just did a fully hermetic and clean build of head of GHC 7.10 branch (what should become 7.10.2), and then brought HP up-to-date: - bootstrapped with 7.10.1 (so hptool needed fixes to build with that) - uses latest shake - built on a clean Debian Wheezy (7) install, (hence uses glibc 2.13 and should also run on Ubuntu 12.04 and later) The package versions are updated as follows: Cabal 1.22.2.0 --> 1.22.3.0 cabal-install 1.22.2.0 --> 1.22.4.0 attoparsec 0.12.1.4 --> 0.13.0.0 syb 0.4.4 --> 0.5.1 text 1.2.0.4 --> 1.2.1.1 cgi 3001.2.2.1 --> 3001.2.2.2 network 2.6.0.2 --> 2.6.2.0 network-uri 2.6.0.1 --> 2.6.0.3 QuickCheck 2.8 --> 2.8.1 hscolour 1.22 --> 1.23 GLUT 2.7.0.0 --> 2.7.0.1 GLURaw 1.5.0.0 --> 1.5.0.1 OpenGL 2.12.0.0 --> 2.12.0.1 OpenGLRaw 2.4.1.0 --> 2.5.0.0 Only package issue was: zlib 0.5.4.2 -- held back because cabal-install needs < 0.6 All the same caveats and notes from Alpha 2 still apply. All these changes are in the pre-release-2 branch on github -- I'll merge it all together later this week. There is a hp-bindist-tarball on my server: haskell-platform-7.10.1.20150528-x86_64-unknown-linux-deb7.tar.gz <http://www.ozonehouse.com/mark/platform/haskell-platform-7.10.1.20150528-x8…> SHA-256: b503c9e2c34c0865b5fee39444027667bb39b786fa7664029287e3bbf33379da I'll build and put up OS X version in a day or two. One last thing... I'm proposing that we name this release: Haskell Platform 7.10.2 ! - Mark

2 8

windows failure in testsuite
by Simon Peyton Jones 10 Jun '15

10 Jun '15

Windows and testsuite folk: The testsuite framework is crashing on my 32-bit Windows machine, with the error below. Happens when the stderr output differs from expected. I know that there have been recent changes in the testsuite stuff. Could you fix please? Thanks Simon =====> T4254(normal) 1587 of 4522 [2, 15, 0] cd ./indexed-types/should_fail && "C:/code/HEAD/inplace/bin/ghc-stage2.exe" -c T4254.hs -fforce-recomp -dcore-lint -dcmm-lint -dno-debug-output -no-user-package-db -rtsopts -fno-warn-tabs -fno-ghci-history > T4254.comp.stderr 2>&1 Actual stderr output differs from expected: 'diff' is not recognized as an internal or external command, operable program or batch file.

2 2

GHC Weekly News - 2015/06/10
by Austin Seipp 10 Jun '15

10 Jun '15

(This post is available online at https://ghc.haskell.org/trac/ghc/blog/weekly20150610) Hi *, Welcome for the latest entry in the GHC Weekly News. The past week, GHC HQ met up for a quick catch up on 7.10.2 (which you'll want to read up on, see below), and some other technical nonsense about some work we've been doing. As a result the current weekly notes have been slow - the current priority is the next release though, which leads us to... == 7.10.2 status == 7.10.2 is '''going to be out soon''' - our current plan is to have a release candidate on '''the weekend of Saturday the 13th''', and the final release '''the next week'''. That means if you want something fixed, you'd better hollar ''very'' soon, or we're just not going to get to it! If you're wondering what's currently been fixed/scheduled, the [https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.10.2 status page] shows the current set of tickets we've fixed and plan on fixing. == List chatter == - Edward Z. Yang has written up a new wiki page to clearly explain and document all the various confusion around package keys, package ids, etc as a result of all the new Backpack work. If you're interested in this, it's definitely worth a read. https://mail.haskell.org/pipermail/ghc-devs/2015-June/009173.html - Mark Lentczner sez: The Haskell Platform has finally outgrown Travis-CI, now going beyond the 50 minute build limit. Mark asks what alternatives we can use going forward. https://mail.haskell.org/pipermail/ghc-devs/2015-June/009174.html - Jan Stolarek asks: in some cases, GHC will generate default instances or values, but that source code has no textual information location (for example, consider an `instance` clause without the `where`) - what do people think about fixing this, and are there anythings to look out for? https://mail.haskell.org/pipermail/ghc-devs/2015-June/009202.html - David Luposchainsky has opened a new thread - about moving `fail` out of `Monad` and into its own typeclass, `MonadFail`. This change is a request that's very long in the tooth (older than the AMP or FTP changes by a landslide), but David's proposal has a clearly set out goal to tackle compatibility, warnings, and implementation. https://mail.haskell.org/pipermail/ghc-devs/2015-June/009186.html == Noteworthy commits == - Commit 19ec6a84d6344c2808d0d41da11956689a0e4ae9 - Fix for CAF retention when dynamically loading & unloading code - Commit 4a0b7a10442eec3747d5f95ef186a79bb0648754 - Build: run autoreconf jobs in parallel == Closed tickets == #10460, #7672, #9252, #9506, #10294, #5316, #10408, #10386, #9960, #10145, #9259, #10386, #9507, #8723, #10442, #5014, #4215, #10443, #8244, #10499, #10500, #10428, #10488, #10489, #10406, #10501, #10441, #10406, #10502, #9101, #9663, and #9945. -- Regards, Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/

1 0

Re: MonadFail proposal (MFP): Moving fail out of Monad
by Carter Schonwald 10 Jun '15

10 Jun '15

i'll add my token +1 to the land slide On Tue, Jun 9, 2015 at 11:19 PM, Bardur Arantsson <spam(a)scientician.net> wrote: > On 06/09/2015 10:43 PM, David Luposchainsky wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > +1 > > _______________________________________________ > Libraries mailing list > Libraries(a)haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries >

1 0

Clearing up confusion about package keys, package ids, et al
by Edward Z. Yang 05 Jun '15

05 Jun '15

I have written a new wiki page which tries to explicate these concepts: https://ghc.haskell.org/trac/ghc/wiki/Commentary/Packages/Concepts I haven't finished writing my proposal but one thing that I am going to argue is that we are going to need *MORE* package identification concepts (sorry Simon!); e.g. reusing package keys as Nix keys just isn't going to work. Edward

1 0

RE: HEADS UP: Final call for 7.10.2 is soon
by Simon Peyton Jones 05 Jun '15

05 Jun '15

| Now that I have a working GHC development environment (which was easier | than thought thanks to the good documentation on the wiki), I am looking | forward to work on ticket #7081 during the summer. When is the | (approximate) deadline for feature patches for GHC 7.12? Great! We don't have a deadline for 7.12 yet. Everyone: when would you *like* 7.12? See https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.12.1 for what might be in it. Simon | -----Original Message----- | From: Wolfgang Jeltsch [mailto:wolfgang@cs.ioc.ee] | Sent: 04 June 2015 18:29 | To: Simon Peyton Jones | Subject: Re: HEADS UP: Final call for 7.10.2 is soon | | Hi again, | | I have successfully set up my GHC development environment and have tried | building incremental-computing with GHC HEAD. And yes, | incremental-computing does go through. :-) Thank you for the good work. | | Now that I have a working GHC development environment (which was easier | than thought thanks to the good documentation on the wiki), I am looking | forward to work on ticket #7081 during the summer. When is the | (approximate) deadline for feature patches for GHC 7.12? | | All the best, | Wolfgang | | Am Mittwoch, den 03.06.2015, 14:20 +0300 schrieb Wolfgang Jeltsch: | > Hi, | > | > I did not try, since I do not have HEAD on my machine and thought that | > it was too difficult and time consuming to install it. I can give it a | > try, hoping that the GHC HEAD installation will be painless. | > | > All the best, | > Wolfgang | > | > Am Mittwoch, den 03.06.2015, 08:57 +0000 schrieb Simon Peyton Jones: | > > Wolfgang: did incremental-computing go through with HEAD? | > > | > > | > > | > > | -----Original Message----- | > > | From: Glasgow-haskell-users [mailto:glasgow-haskell-users- | > > | bounces(a)haskell.org] On Behalf Of Wolfgang Jeltsch | > > | Sent: 02 June 2015 23:03 | > > | To: glasgow-haskell-users(a)haskell.org | > > | Subject: Re: HEADS UP: Final call for 7.10.2 is soon | > > | | > > | Hi, | > > | | > > | bug #10009 appears on the status page with status “new”, although | the | > > | bug should have been fixed in HEAD. Can this fix *please* be a | part of | > > | GHC 7.10.2? At the moment, this bug breaks the incremental- | computing | > > | package in a nontrivial way (and I think it breaks HList too). | > > | | > > | All the best, | > > | Wolfgang | > > | | > > | Am Dienstag, den 02.06.2015, 16:31 -0500 schrieb Austin Seipp: | > > | > Hi *, | > > | > | > > | > I've just finished merging all the latest patches for GHC 7.10.2 | > > | into | > > | > the STABLE branch. All in all, we've fixed a lot of bugs (over | 80 | > > | > tickets closed)! | > > | > | > > | > So, we'll probably be doing a 7.10.2 release here in a few | weeks. | > > | The | > > | > tentative plan was around the 14th, although it's not set in | stone. | > > | > (At worst, it would be pushed from the 14th to the 21st). | > > | > | > > | > With that in mind, if I could quickly direct your attention to | the | > > | GHC | > > | > bug tracker and the status page[1] - it would be really helpful | if | > > | you | > > | > check if the things you want are fixed! | > > | > | > > | > Specifically, if you want something fixed for the 7.10.2 | release: | > > | > | > > | > - Make sure there is a ticket. It really needs to exist or | we'll | > > | just forget! | > > | > | > > | > - If your bug is critical, please explain why! We really want | to | > > | > kill showstoppers ASAP, because bugs are much cheaper to fix | early. | > > | If | > > | > that's the case we can bump the priority if it's necessary to | make | > > | > things clear. | > > | > | > > | > - Set the milestone to 7.10.2. It'll automatically appear on | the | > > | status page. | > > | > | > > | > That should be it - we'll be monitoring the status page | regularly to | > > | > keep track of new things. The current bug list is pretty small - | we | > > | > may move some of them out, or fix several more. So just try to | let | > > | us | > > | > know. | > > | > | > > | > As a sidenote, I'm quite happy with this release - it's fixed | dozens | > > | > of tricky bugs, improved some nasty corner cases in compiler | > > | > performance, and overall seems like it will be high quality. | Thanks | > > | to | > > | > everyone who submitted patches! | > > | > | > > | > I'll send out another email next week as another reminder. | > > | > | > > | > [1] https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.10.2 | > > | > | > > | | > > | | > > | _______________________________________________ | > > | Glasgow-haskell-users mailing list | > > | Glasgow-haskell-users(a)haskell.org | > > | http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell- | users | > |

2 1

HEADS UP: Final call for 7.10.2 is soon
by Austin Seipp 05 Jun '15

05 Jun '15

Hi *, I've just finished merging all the latest patches for GHC 7.10.2 into the STABLE branch. All in all, we've fixed a lot of bugs (over 80 tickets closed)! So, we'll probably be doing a 7.10.2 release here in a few weeks. The tentative plan was around the 14th, although it's not set in stone. (At worst, it would be pushed from the 14th to the 21st). With that in mind, if I could quickly direct your attention to the GHC bug tracker and the status page[1] - it would be really helpful if you check if the things you want are fixed! Specifically, if you want something fixed for the 7.10.2 release: - Make sure there is a ticket. It really needs to exist or we'll just forget! - If your bug is critical, please explain why! We really want to kill showstoppers ASAP, because bugs are much cheaper to fix early. If that's the case we can bump the priority if it's necessary to make things clear. - Set the milestone to 7.10.2. It'll automatically appear on the status page. That should be it - we'll be monitoring the status page regularly to keep track of new things. The current bug list is pretty small - we may move some of them out, or fix several more. So just try to let us know. As a sidenote, I'm quite happy with this release - it's fixed dozens of tricky bugs, improved some nasty corner cases in compiler performance, and overall seems like it will be high quality. Thanks to everyone who submitted patches! I'll send out another email next week as another reminder. [1] https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.10.2 -- Regards, Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/

3 2

StrictData and the parser
by Adam Sandberg Eriksson 05 Jun '15

05 Jun '15

Hello *, I'm working on the -XStrict language extension[1] for this years Google summer of code. I've started with the smaller -XStrictData (as documented at the wiki) and have the internals mostly figured out. However after adding relevant rules for '~' in the parser[2] I get an explosion of shift/reduce conflicts as well as 4 extra reduce/reduce conflicts, see [3] for the happy info (the states with 36 shift/reduce conflicts seem to be the problematic ones), I also fail to parse the test file [4] with the error DsStrictData.hs:15:1: error: parse error (possibly incorrect indentation or mismatched brackets) Can anyone offer some guidance on what the appropriate changes to the parser are to make these "lazyness" marks work? Thanks, Adam [1]: https://ghc.haskell.org/trac/ghc/wiki/StrictPragma [2]: https://github.com/adamse/ghc/blob/strict-pragma/compiler/parser/Parser.y#L… [3]: https://gist.githubusercontent.com/adamse/8d6c54b6ae660fca8b97/raw/detailed… [4]: https://github.com/adamse/ghc/blob/strict-pragma/testsuite/tests/deSugar/sh… -- Adam Sandberg Eriksson

5 7

MSYS2 package for GHC 7.10.1
by David Macek 04 Jun '15

04 Jun '15

Hi everyone. After finally putting some uninterruped effort into it, I managed to create (hopefully) working prototypes of two GHC-related packages for MSYS2, namely ghc[1] and cabal-install[2]. I've prepared recipes (PKGBUILDs) for building from source, but 64-bit binaries[5][6] are also provided for those who'd like to test my build without building it themselves. With this post, I'd like to start some work towards the following goals (I hope we can get some Windows discussion going again): - verify that the build is reproducible (see below for instructions) - make tests pass - fix known issues (see below for list) - discover and fix unknown issues - review and upstream as many patches as possible - make it easier for people on Windows to start hacking on GHC I'll be glad to read any responses, notes, results, hints, comments and/or criticisms. Please note that I'm writing this after being submerged in the matter for some time, so don't be surprised to see any glaring omissions or obvious mistakes. Known issues ============ Configure has a problem with docbook - This mean Haddock is not built. It's probably some silliness on the part of MSYS2's docbook. Integer-gmp object file has a reference to __mingw_vsnprintf - Compiling seems to work fine, presumably because the final link command includes -lmingwex, but `runhaskell Setup.lhs` in the text package source tree gave me an undefined reference error, causing inability to load integer-gmp module. I don't know where to start fixing this, as I have not yet reached the depth of understanding of GHC source needed for that. Wildly untested - I didn't try building with LLVM and the testsuite is currently failing to start, giving some weird errors. Trying cross compiling or compiling a cross compiler didn't even cross my mind (har har). Patches ======= A lot of the patches deal with the directory structure -- I tried to mirror the common FHS layout as closely as possible while still retaining the advantages of relocatability. I also removed the bundled toolchain and perl, in favor of packages included with MSYS2. I assume these changes are somewhat controversial for upstreaming, but it'd be nice to see the official bindists to adopt this layout. There are several patches that I think are more of straight-forward fixes rather than design changes, namely numbers 0007, 0010, 0014 and 0015. Build instructions ================== General build instructions[3] are available at our wiki. For convenience, I've compiled a sequence of commands that should get you the ghc and cabal-install packages, given that you start with an up-to-date installation of MSYS2 and a working GHC in PATH. Refer to our guide[4] for correct way of getting/upgrading your MSYS2. ## start MSYS2 shell pacman --needed -S base-devel mingw-w64-x86_64-toolchain mingw-w64-i686-toolchain git clone https://github.com/elieux/mingw-packages cd mingw-packages git checkout ghc pushd mingw-w64-ghc makepkg-mingw -sLf pacman -U mingw-w64-*-ghc-*-any.pkg.tar.xz ## remove old GHC from PATH popd pushd mingw-w64-cabal-install makepkg-mingw -sLf pacman -U mingw-w64-*-cabal-install-*-any.pkg.tar.xz popd If you prefer to build only for one architecture, export a variable named MINGW_INSTALLS with a value of "mingw32" or "mingw64" before building. == [1] https://github.com/elieux/mingw-packages/tree/ghc/mingw-w64-ghc [2] https://github.com/elieux/mingw-packages/tree/ghc/mingw-w64-cabal-install [3] http://sourceforge.net/p/msys2/wiki/Contributing%20to%20MSYS2/ [4] http://sourceforge.net/p/msys2/wiki/MSYS2%20installation/ [5] https://dl.dropboxusercontent.com/u/59899181/mingw-w64-x86_64-cabal-install… [6] https://dl.dropboxusercontent.com/u/59899181/mingw-w64-x86_64-ghc-7.10.1-1-… -- David Macek

3 5

archive of old ghc nightly builds?
by malcolm.wallace 04 Jun '15

04 Jun '15

I'm looking for an archive of ghc nightly builds, so I can bisect a suspected bug at least to a small date range. Does such an archive exist? I have colleagues who say they used such an archive, and fairly recently, but we can't seem to find it from the ghc dev wiki today. The date range I am hoping for is roughly Sept 2012 to April 2014. Regards, Malcolm

1 0