- ghc-devs - Haskell.org

Releasing containers 0.5.3.2 -- before GHC 7.8?
by Ryan Newton 16 Jan '14

16 Jan '14

Hi guys, I'm wondering if we can do a hackage release of 0.5.3.2? That "splitRoot" function is in there, and my ability to deploy parallel code that uses containers depends on people getting it! Are there any other changes since 0.5.3.1? Replacing containers seems like a real pain for end users, so it would be great if 0.5.3.2 could come with GHC 7.8. Currently, it looks like the GHC repo is up to date in that it includes 0.5.3.1. I realize it is late days for this, but: - It's been a month since we put splitRoot in; I've been using it heavily and it I'm pretty confident that it's correct. (It's so simple!) - Nothing else is touched, so there is very little liability associated with this version bump. And, as you know, if we don't make this round it's a long latency before the next chance. That is, before we can expect people to do parallel folds over Data.Set or Data.Map without installation headache. Any objections? -Ryan

5 6

PLT Redex definition of STG as per fast curry paper
by Edward Z. Yang 15 Jan '14

15 Jan '14

For those of you who aren't following the commit list, I've just pushed a PLT Redex <http://redex.racket-lang.org/> definition for an STG-like language as was defined in the fast curry paper. This language is *not* STG. The hope is that this will be a good starting point for actually formalizing STG as it exists today. I've included a hefty comment block at the top of the development summarizing ways in which this could be improved. Take a look if you're interested! Cheers, Edward

3 2

ghci verbosity
by Simon Peyton Jones 15 Jan '14

15 Jan '14

Friends ghc -interactive has just started being more verbose. The "linking...done" stuff didn't happen before. Does this ring any bells for anyone? I have not investigated at all so far; hoping someone will say "oh yes, I know and will fix". Simon bash$ ~/5builds/HEAD/inplace/bin/ghc-stage2 --interactive GHCi, version 7.7.20140114: http://www.haskell.org/ghc/ :? for help Loading package ghc-prim ... linking ... done. Loading package integer-gmp ... linking ... done. Loading package base ... linking ... done. Prelude>

3 3

Re: Releasing containers 0.5.3.2 -- before GHC 7.8?
by Johan Tibell 14 Jan '14

14 Jan '14

I'll make a release in the next few days. On Tue, Jan 14, 2014 at 10:33 PM, Milan Straka <fox(a)ucw.cz> wrote: > Hi Johan, > > I think releasing 0.5.4 is a good idea. Could I ask you to do the > release as usual, please? > > We added the splitRoot function, so it should really be 0.5.4 and not > only 0.5.3.2. Actually, we added Functor instance to Graph.SCC and > Functor and Applicative instances to Graph.SetM, but Graph is rarely > used, so I would deliberately break PVP and not do a major version bump. > > Thanks, > cheers, > Milan > > > -----Original message----- > > From: Ryan Newton <rrnewton(a)gmail.com> > > Sent: 14 Jan 2014, 11:41 > > > > Hi guys, > > > > I'm wondering if we can do a hackage release of 0.5.3.2? That > "splitRoot" > > function is in there, and my ability to deploy parallel code that uses > > containers depends on people getting it! Are there any other changes > since > > 0.5.3.1? > > > > Replacing containers seems like a real pain for end users, so it would be > > great if 0.5.3.2 could come with GHC 7.8. Currently, it looks like the > GHC > > repo is up to date in that it includes 0.5.3.1. > > > > I realize it is late days for this, but: > > > > - It's been a month since we put splitRoot in; I've been using it > > heavily and it I'm pretty confident that it's correct. (It's so > simple!) > > - Nothing else is touched, so there is very little liability > associated > > with this version bump. > > > > And, as you know, if we don't make this round it's a long latency before > > the next chance. That is, before we can expect people to do parallel > folds > > over Data.Set or Data.Map without installation headache. > > > > Any objections? > > -Ryan >

1 0

Folding constants for floats
by Kyle Van Berendonck 14 Jan '14

14 Jan '14

Hi, I'm cutting my teeth on some constant folding for floats in the cmm. I have a question regarding the ticket I'm tackling: Should floats be folded with infinite precision (and later truncated to the platform float size) -- most useful/accurate, or folded with the platform precision, i.e. double, losing accuracy but keeping consistent behaviour with -O0 -- most "correct"? I would prefer the first case because it's *much* easier to implement than the second, and it'll probably rot less. Regards.

4 12

Fwd: Re: Pattern synonyms for 7.8?
by Dr. ÉRDI Gergő 14 Jan '14

14 Jan '14

Hi, How do I get permissions to push to my wip branch? Thanks, Gergo ---------- Forwarded message ---------- From: "Dr. ERDI Gergo" <gergo(a)erdi.hu> Date: Jan 13, 2014 8:12 PM Subject: Re: Pattern synonyms for 7.8? To: <austin(a)well-typed.com> Cc: "Gabor Greif" <ggreif(a)gmail.com> (removing Mateusz and ghc-devs from the recipient list) Hi, On Mon, 13 Jan 2014, Gabor Greif wrote: From what I understood, you *should* have all permissions to push to > wip/ branches. If not, please contact the admins. (IIRC Austin did > this previously). > OK, I think this was the missing information that got me confused. What repo are we talking about? I tried the mirror on GitHub (git@github.com:ghc/ghc.git) but that one doesn't seem to work: ERROR: Permission to ghc/ghc.git denied to gergoerdi. fatal: Could not read from remote repository. I also tried the Haskell.org repo of ssh://git@git.haskell.org/ghc, but that doesn't work either (which is unsurprising since I don't remember ever sending my SSH public key to haskell.org) 20:10:02 [cactus@galaxy ghc]$ git push -u origin wip/pattern-synonyms Permission denied (publickey). Please advise. Thanks, Gergo -- .--= ULLA! =-----------------. \ http://gergo.erdi.hu \ `---= gergo(a)erdi.hu =-------' Ki volt Casper, mielôtt meghalt?

1 0

Quick code style question: Wild card binders
by Joachim Breitner 14 Jan '14

14 Jan '14

Hi, both work, so it is a matter of style, and I’m not sure which one is better style: If I generate a Case where the case binder is not used, should I * use the wildcard binder (mkWildCase), to be explicit about the fact fact that the wildcard binder is unused, or should I * generate a new Unique and a new Id nevertheless, because wildCard is bad? Thanks, Joachim -- Joachim “nomeata” Breitner mail(a)joachim-breitner.de • http://www.joachim-breitner.de/ Jabber: nomeata(a)joachim-breitner.de • GPG-Key: 0x4743206C Debian Developer: nomeata(a)debian.org

1 1

Enable TypeHoles by default?
by Krzysztof Gogolewski 13 Jan '14

13 Jan '14

Hello, I propose to enable -XTypeHoles in GHC by default. Unlike other -X* flags, holes do not really change meaning of the program, they only change error messages. Instead of "_x not in scope", we effectively get "_x not in scope, its expected type is a -> a". You get it only if you precede the identifier not in scope with underscore, so in some sense you declare the intention of using holes. Two possible issues: (a) If you use -fdefer-type-errors, then a program might compile, while previously it did not. However, we should facilitate compiling with defer-type-errors, so I don't think this is a disadvantage. (b) The identifier _ becomes both a pattern and a hole by default, which might confuse new users. Reply: I have never seen anyone ask why code such as "Just _ -> _" does not work. IMO the productivity boost by having holes by default outweighs those two objections. I am open to hearing any other possible issues others might find. The change is trivial implementation-wise; add Opt_TypeHoles to the list in languageExtensions Nothing in DynFlags. -KG

9 11

High-level Cmm code and stack allocation
by Herbert Valerio Riedel 13 Jan '14

13 Jan '14

Hello, According to Note [Syntax of .cmm files], | There are two ways to write .cmm code: | | (1) High-level Cmm code delegates the stack handling to GHC, and | never explicitly mentions Sp or registers. | | (2) Low-level Cmm manages the stack itself, and must know about | calling conventions. | | Whether you want high-level or low-level Cmm is indicated by the | presence of an argument list on a procedure. However, while working on integer-gmp I've been noticing in integer-gmp/cbits/gmp-wrappers.cmm that even though all Cmm procedures have been converted to high-level Cmm, they still reference the 'Sp' register, e.g. #define GMP_TAKE1_RET1(name,mp_fun) \ name (W_ ws1, P_ d1) \ { \ W_ mp_tmp1; \ W_ mp_result1; \ \ again: \ STK_CHK_GEN_N (2 * SIZEOF_MP_INT); \ MAYBE_GC(again); \ \ mp_tmp1 = Sp - 1 * SIZEOF_MP_INT; \ mp_result1 = Sp - 2 * SIZEOF_MP_INT; \ ... \ So is this valid high-level Cmm code? What's the proper way to allocate Stack (and/or Heap) memory from high-level Cmm code? Cheers, hvr

5 19

testsuite change
by Simon Peyton Jones 13 Jan '14

13 Jan '14

Herbert I did 'git pull' in my source tree and got the error below. What do I do now? Simon == running git pull remote: Counting objects: 56029, done. remote: Compressing objects: 100% (16843/16843), done. remote: Total 55837 (delta 32572), reused 55743 (delta 32500) Receiving objects: 100% (55837/55837), 6.47 MiB | 2.96 MiB/s, done. Resolving deltas: 100% (32572/32572), completed with 102 local objects. >From git://git.haskell.org/ghc b7ddf63..9c91a24 master -> origin/master Updating b7ddf63..9c91a24 error: The following untracked working tree files would be overwritten by merge: testsuite/.gitignore testsuite/LICENSE testsuite/LICENSE.GPL testsuite/Makefile testsuite/README.md testsuite/config/bad.ps testsuite/config/ghc testsuite/config/good.ps testsuite/driver/runtests.py testsuite/driver/testglobals.py testsuite/driver/testlib.py testsuite/driver/testutil.py testsuite/mk/boilerplate.mk testsuite/mk/ghc-config.hs testsuite/mk/test.mk testsuite/tests/Makefile testsuite/tests/annotations/Makefile testsuite/tests/annotations/should_compile/Makefile testsuite/tests/annotations/should_compile/all.T testsuite/tests/annotations/should_compile/ann01.hs testsuite/tests/annotations/should_compile/ann01.stderr testsuite/tests/annotations/should_fail/Annfail04_Help.hs testsuite/tests/annotations/should_fail/Annfail05_Help.hs testsuite/tests/annotations/should_fail/Annfail06_Help.hs testsuite/tests/annotations/should_fail/Makefile testsuite/tests/annotations/should_fail/all.T testsuite/tests/annotations/should_fail/annfail01.hs testsuite/tests/annotations/should_fail/annfail01.stderr testsuite/tests/annotations/should_fail/annfail02.hs testsuite/tests/annotations/should_fail/annfail02.stderr testsuite/tests/annotations/should_fail/annfail03.hs testsuite/tests/annotations/should_fail/annfail03.stderr testsuite/tests/annotations/should_fail/annfail04.hs testsuite/tests/annotations/should_fail/annfail04.stderr testsuite/tests/annotations/should_fail/annfail05.hs testsuite/tests/annotations/should_fail/annfail05.stderr testsuite/tests/annotations/should_fail/annfail06.hs testsuite/tests/annotations/should_fail/annfail06.stderr testsuite/tests/annotations/should_fail/annfail07.hs testsuite/tests/annotations/should_fail/annfail07.stderr testsuite/tests/annotations/should_fail/annfail08.hs testsuite/tests/annotations/should_fail/annfail08.stderr testsuite/tests/annotations/should_fail/annfail09.hs testsuite/tests/annotations/should_fail/annfail09.stderr testsuite/tests/annotations/should_fail/annfail10.hs testsuite/tests/annotations/should_fail/annfail10.stderr testsuite/tests/annotations/should_fail/annfail11.hs testsuite/tests/annotations/should_fail/annfail11.stderr testsuite/tests/annotations/should_fail/annfail12.hs testsuite/tests/annotations/should_fail/annfail12.stderr testsuite/tests/annotations/should_fail/annfail13.hs testsuite/tests/annotations/should_fail/annfail13.stderr testsuite/tests/annotations/should_run/Annrun01_Help.hs testsuite/tests/annotations/should_run/Makefile testsuite/tests/annotations/should_run/all.T testsuite/tests/annotations/should_run/annrun01.hs testsuite/tests/annotations/should_run/annrun01.stdout testsuite/tests/arityanal/Main.hs testsuite/tests/arityanal/Main.stderr testsuite/tests/arityanal/Makefile testsuite/tests/arityanal/f0.hs testsuite/tests/arityanal/f0.stderr testsuite/tests/arityanal/f1.hs testsuite/tests/arityanal/f1.stderr testsuite/tests/arityanal/f10.hs testsuite/tests/arityanal/f10.stderr testsuite/tests/arityanal/f11.hs testsuite/tests/arityanal/f11.stderr testsuite/tests/arityanal/f12.hs testsuite/tests/arityanal/f12.stderr testsuite/tests/arityanal/f13.hs testsuite/tests/arityanal/f13.stderr testsuite/tests/arityanal/f14.hs testsuite/tests/arityanal/f14.stderr testsuite/tests/arityanal/f15.hs testsuite/tests/arityanal/f15.stderr testsuite/tests/arityanal/f2.hs testsuite/tests/arityanal/f2.stderr testsuite/tests/arityanal/f3.hs testsuite/tests/arityanal/f3.stderr testsuite/tests/arityanal/f4.hs testsuite/tests/arityanal/f4.stderr testsuite/tests/arityanal/f5.hs testsuite/tests/arityanal/f5.stderr testsuite/tests/arityanal/f6.hs testsuite/tests/arityanal/f6.stderr testsuite/tests/arityanal/f7.hs testsuite/tests/arityanal/f7.stderr testsuite/tests/arityanal/f8.hs testsuite/tests/arityanal/f8.stderr testsuite/tests/arityanal/f9.hs testsuite/tests/arityanal/f9.stderr testsuite/tests/arityanal/prim.hs testsuite/tests/arityanal/prim.stderr testsuite/tests/array/Makefile testsuite/tests/array/shou Aborting git failed: 256 at ./sync-all line 120. == Checking for old haddock repo == Checking for old binary repo == Checking for old mtl repo == Checking for old Cabal repo == Checking for old time from tarball == Checking for obsolete Git repo URL simonpj@cam-05-unx:~/code/HEAD-2$

2 4