June 2015 - ghc-devs - Haskell.org

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

Consecutive FFI calls
by David Turner 03 Jun '15

03 Jun '15

Hi, If I make a sequence of FFI calls (on a single Haskell thread) but which end up being called from different OS threads, is there any kind of ordering guarantee given? More specifically, is there a full memory barrier at the point where a Haskell thread migrates to a new OS thread? Many thanks, David

3 5

RE: [Diffusion] [Build Failed] rGHC7ea156ae3e1c: Refactor RdrName.Provenance, to fix #7672
by Simon Peyton Jones 03 Jun '15

03 Jun '15

I'm still seeing Unexpected stat failures: perf/haddock haddock.compiler [stat not good enough] (normal) but only on Phab not on my own machine. I don't know how to fix this. Simon | -----Original Message----- | From: noreply(a)phabricator.haskell.org | [mailto:noreply@phabricator.haskell.org] | Sent: 03 June 2015 12:27 | To: Simon Peyton Jones | Subject: [Diffusion] [Build Failed] rGHC7ea156ae3e1c: Refactor | RdrName.Provenance, to fix #7672 | | Harbormaster failed to build B4245: rGHC7ea156ae3e1c: Refactor | RdrName.Provenance, to fix #7672! | | BRANCHES | master | | USERS | simonpj (Author) | GHC - Testsuite (Auditor) | GHC - Core/System FC (Auditor) | GHC - Driver (Auditor) | GHC - Renamer (Auditor) | GHC - Type checker/inferencer (Auditor) | | COMMIT | https://phabricator.haskell.org/rGHC7ea156ae3e1c | | EMAIL PREFERENCES | https://phabricator.haskell.org/settings/panel/emailpreferences/ | | To: simonpj, GHC - Testsuite, GHC - Core/System FC, GHC - Driver, GHC | - Renamer, GHC - Type checker/inferencer

1 0

Re: [commit: ghc] master: build: make haddock a bit less chatty (e796026)
by Mateusz Kowalczyk 03 Jun '15

03 Jun '15

On 06/02/2015 03:31 PM, git(a)git.haskell.org wrote: > Repository : ssh://git@git.haskell.org/ghc > > On branch : master > Link : http://ghc.haskell.org/trac/ghc/changeset/e796026b45974d71233eef7ffb6feee48… > >> --------------------------------------------------------------- > > commit e796026b45974d71233eef7ffb6feee482c6dd7e > Author: Austin Seipp <austin(a)well-typed.com> > Date: Tue Jun 2 09:31:52 2015 -0500 > > build: make haddock a bit less chatty > > Summary: > Haddock outputs well over a thousand lines of file output just to give > its executive summary about coverage. Kill this by default, since we > really don't need it in any setting. > > Signed-off-by: Austin Seipp <austin(a)well-typed.com> > > Test Plan: Crossed my fingers. > > Reviewers: nomeata, thomie > > Reviewed By: thomie > > Subscribers: bgamari, thomie > > Differential Revision: https://phabricator.haskell.org/D933 > > >> --------------------------------------------------------------- > > e796026b45974d71233eef7ffb6feee482c6dd7e > ghc.mk | 2 +- > rules/haddock.mk | 1 + > 2 files changed, 2 insertions(+), 1 deletion(-) > > diff --git a/ghc.mk b/ghc.mk > index 5a1845c..3b38372 100644 > --- a/ghc.mk > +++ b/ghc.mk > @@ -1375,7 +1375,7 @@ validate_build_xhtml: > cd libraries/xhtml && ./Setup configure --with-ghc="$(BINDIST_PREFIX)/bin/ghc" $(BINDIST_HADDOCK_FLAG) $(BINDIST_LIBRARY_FLAGS) --global --builddir=dist-bindist --prefix="$(BINDIST_PREFIX)" > cd libraries/xhtml && ./Setup build --builddir=dist-bindist > ifeq "$(HADDOCK_DOCS)" "YES" > - cd libraries/xhtml && ./Setup haddock --ghc-options=-optP-P --builddir=dist-bindist > + cd libraries/xhtml && ./Setup haddock -v0 --ghc-options=-optP-P --builddir=dist-bindist > endif > cd libraries/xhtml && ./Setup install --builddir=dist-bindist > cd libraries/xhtml && ./Setup clean --builddir=dist-bindist > diff --git a/rules/haddock.mk b/rules/haddock.mk > index a43df95..5604a50 100644 > --- a/rules/haddock.mk > +++ b/rules/haddock.mk > @@ -48,6 +48,7 @@ ifeq "$$(HSCOLOUR_SRCS)" "YES" > "$$(ghc-cabal_INPLACE)" hscolour $1 $2 > endif > "$$(TOP)/$$(INPLACE_BIN)/haddock" \ > + --verbosity=0 \ > --odir="$1/$2/doc/html/$$($1_PACKAGE)" \ > --no-tmp-comp-dir \ > --dump-interface=$$($$($1_PACKAGE)-$$($1_$2_VERSION)_HADDOCK_FILE) \ > > _______________________________________________ > ghc-commits mailing list > ghc-commits(a)haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-commits > You could have just used --no-print-missing-docs to go to the old amount of output. Or start filling out the stuff Haddock is complaining about, I made it a default to nag people :) -- Mateusz K.

1 0

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

03 Jun '15

(This post is available online at https://ghc.haskell.org/trac/ghc/blog/weekly20150603) Hi *, It's that time once again - to get some info on what's happening in the world of GHC! It's been a quiet few weeks as a UK Holiday punted one of GHC HQ's meetings off, and this week we were only partially there. The main point of discussion was 7.10.2, and continuing work on compiler performance. The good news is, the past few weeks have seen good work on both these fronts! == 7.10.2 status == 7.10.2 is swimming along very nicely - 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. Not much has changed from last time, except we've fixed even more bugs! We're currently sitting at about 85 bugs fixed, some of them pretty important - code generation bugs, compiler performance fixes, some RTS and event manager work. Your author is actually quite happy with what GHC 7.10.2 looks like, at this rate. == List chatter == - Austin Seipp announced that GHC 7.10.2 will be release soon, and developers/users should get bugs they want fixed reported to us ASAP so we can do something. https://mail.haskell.org/pipermail/ghc-devs/2015-June/009150.html - Mark Lentczner announced a Haskell Platform alpha featuring GHC 7.10.2 https://mail.haskell.org/pipermail/ghc-devs/2015-June/009128.html - Facundo Dominguez asks: sometimes we want to create a `static` pointer in a function with a local definition, how can we do that? The current problem is the desugarer gets in the way and current approaches are currently rejected, but Facundo has some ideas/questions about a fix. https://mail.haskell.org/pipermail/ghc-devs/2015-May/009110.html - David Macek has made great progress on getting native MSYS2 packages for windows working - which should be a great boon to all our Windows users! https://mail.haskell.org/pipermail/ghc-devs/2015-May/009089.html - Joachim Breitner announced the new GHC performance dashboard, which can be used to track all of GHC's performance-based tests over time. Whoohoo! https://mail.haskell.org/pipermail/ghc-devs/2015-May/009032.html - Joachim Breitner asked: is there a way to programmatically 'Raise a Concern' on a Phabricator commit? With the new https://perf.haskell.org/ghc/ work, it'd be nice if regressions could be automatically flagged. The current problem is there is no API endpoint, but one can be built. https://mail.haskell.org/pipermail/ghc-devs/2015-June/009128.html - Adam Gundry asked ghc-devs about some input on changes to the new typechecker plugins API. After some discussion and elbow grease, the new changes have already landed in HEAD and will be in 7.12.1. https://mail.haskell.org/pipermail/ghc-devs/2015-May/009097.html == Noteworthy commits == - Commit 45d9a15c4b85a2ed89579106bdafd84accf2cb39 - Fix a huge space leak in the mighty simplifier - Commit c89bd681d34d3339771ebdde8aa468b1d9ab042b - Fix quadratic behavior in `tidyOccName` - Commit b03f074fd51adfb9bc4f5275294712ee62741aed - ghci: Allow `:back` and `:forward` to take counts - Commit 8e4dc8fb63b8d3bfee485c1c830776f3ed704f4d - Greatly speed up `nativeCodeGen/seqBlocks` - Commit c256357242ee2dd282fd0516260edccbb7617244 - Speed up `elimCommonBlocks` by grouping blocks also by outgoing labels - Commit f5188f3acd73a07b648924a58b9882c2d0a3dbcb - Fix weird behavior of `-ignore-dot-ghci` and `-ghci-script` - Commit 4fffbc34c024231c3c9fac7a2134896cc09c7fb7 - New handling of overlapping instances in Safe Haskell - Commit f16ddcee0c64a92ab911a7841a8cf64e3ac671fd - Support stage 1 Template Haskell (non-quasi) quotes, fixes #10382 - Commit cf7573b8207bbb17c58612f3345e0b17d74cfb58 - More accurate allocation stats for `:set -s` == Closed tickets == #10407, #10408, #10177, #10359, #10403, #10248, #9579, #10415, #10419, #10427, #10429, #10397, #10422, #10335, #10366, #10110, #10397, #10349, #10244, #8555, #8799, #9131, #10396, #10354, #10278, #9899, #3533, #9950, #10092, #9950, #10430, #9682, #9584, #10446, #10410, #10298, #10449, #10399, #7695, #10261, #8292, #10360, #10126, #10317, #10101, #10322, #10313, #10471, #10473, #7170, #10473, #10423, #10466, #8695, #10461, #10052, #10370, #10425, #10452, #10474, -- Regards, Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/

1 0