pgj-freebsd-amd64-stable (amd64 FreeBSD STABLE), build 413
Build succeeded
Details:
http://darcs.haskell.org/ghcBuilder/builders/pgj-freebsd-amd64-stable/413.html
git clone| Success
create mk/build.mk | Success
get subrepos | Success
repo versions| Success
setting v
pgj-freebsd-i386-stable (x86 FreeBSD STABLE), build 396
Build succeeded
Details:
http://darcs.haskell.org/ghcBuilder/builders/pgj-freebsd-i386-stable/396.html
git clone| Success
create mk/build.mk | Success
get subrepos | Success
repo versions| Success
setting versi
pgj2 (amd64 FreeBSD HEAD), build 531
Build succeeded
Details: http://darcs.haskell.org/ghcBuilder/builders/pgj2/531.html
git clone| Success
create mk/build.mk | Success
get subrepos | Success
repo versions| Success
setting version date | Success
booting
pgj (x86 FreeBSD HEAD), build 533
Build succeeded
Details: http://darcs.haskell.org/ghcBuilder/builders/pgj/533.html
git clone| Success
create mk/build.mk | Success
get subrepos | Success
repo versions| Success
setting version date | Success
booting | Su
Build description = HEAD on x86_64-unknown-linux (cam-04-unx)
Build location= /64playpen/simonmar/nightly/HEAD-cam-04-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-04-unx
Nightly build started on cam-04-unx at Mon Nov 14 18:00:02 GMT 2011.
checking out new source
Build description = STABLE on x86_64-unknown-linux (cam-04-unx)
Build location= /64playpen/simonmar/nightly/STABLE-cam-04-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-STABLE-cam-04-unx
Nightly build started on cam-04-unx at Mon Nov 14 18:10:02 GMT 2011.
checking out new s
On 14.11 12:40, Simon Peyton-Jones wrote:
> | I'm a bit confused about variable shadowing in Core. Since every variable
> has a
> | Unique I would've thought that there is no problem with that (i.e. a Unique
> is
> | globally unique).
>
> No, as Max says, there is *not* a "no-shadowing" invarian
Great thanks everyone!
On 14 November 2011 04:38, Simon Peyton-Jones wrote:
> If you wanted to write a Wiki page in the Commentary summarising your
> understanding, I'd be happy to check it over. Think of the page you'd *like*
> to have read rather than working it out by experiment.
Sure. I'm
simonmar-win32-head (x86 Windows HEAD), build 444
Build failed
Details:
http://darcs.haskell.org/ghcBuilder/builders/simonmar-win32-head/444.html
git clone | Failure: Just (ExitFailure 128)
Build failed
Details:
http://darcs.haskell.org/ghcBuilder/builders/simonmar-win32-head/444.html
fatal:
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : ghc-constraint-solver
http://hackage.haskell.org/trac/ghc/changeset/4832871c1ce77d9b63187014a71e845b89b6227b
>---
commit 4832871c1ce77d9b63187014a71e845b89b6227b
Author:
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/1ae2f142a962647e457d5d6c412997dc81dd3e88
>---
commit 1ae2f142a962647e457d5d6c412997dc81dd3e88
Author: Simon Mar
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/0a7cd204d8069d458b5bfb40372c07d9524180d1
>---
commit 0a7cd204d8069d458b5bfb40372c07d9524180d1
Author: Simon Mar
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/b28d9ebf54f729dc56c20da6cd5863e31e8e5821
>---
commit b28d9ebf54f729dc56c20da6cd5863e31e8e5821
Author: Simon Mar
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/59dbed781a3182435e9d5b251a34bafecfea80fb
>---
commit 59dbed781a3182435e9d5b251a34bafecfea80fb
Author: Simon Mar
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/3f5a0929c7aa5a5dafc06aca18a69ba2e693ae4f
>---
commit 3f5a0929c7aa5a5dafc06aca18a69ba2e693ae4f
Author: Simon Mar
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/d14a5cd2f90d51c4988eae53ea1401cfd843e1eb
>---
commit d14a5cd2f90d51c4988eae53ea1401cfd843e1eb
Author: Simon Mar
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/d71c537632c36b037c3dc7c74686fc18c547c6e9
>---
commit d71c537632c36b037c3dc7c74686fc18c547c6e9
Author: Simon Mar
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/66962374847686e84692ce319a1427e96ac8440c
>---
commit 66962374847686e84692ce319a1427e96ac8440c
Author: Simon Marlow
D
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/e37893cbe8c289dc56cecf6dff5c8b64ed8c3485
>---
commit e37893cbe8c289dc56cecf6dff5c8b64ed8c3485
Author: Simon Marlow
D
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/d2729dc2f7d68838922dfb2c2399a57c96669d93
>---
commit d2729dc2f7d68838922dfb2c2399a57c96669d93
Author: Simon Marlow
D
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/c29c28a463cd3ea86cb0cfa7d3d42c01f2923d4b
>---
commit c29c28a463cd3ea86cb0cfa7d3d42c01f2923d4b
Author: Simon Marlow
D
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/652e3cb2fdd0f1670cf97c94dcc7a08477f5e5c5
>---
commit 652e3cb2fdd0f1670cf97c94dcc7a08477f5e5c5
Author: Simon Marlow
D
On Mon, 14 Nov 2011 08:06:19 +, Simon Peyton-Jones
wrote:
> | It would be nice if the compiler could apply SPECIALIZE pragmas
> | recursively. For example, if I have a polymorphic function f which calls
> | polymorphic functions g and h, it would be nice if one could apply a
> | SPECIALIZE pr
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : ghc-kinds
http://hackage.haskell.org/trac/ghc/changeset/2a4494b5147651d33e2f021f35b83c6a88906426
>---
commit 2a4494b5147651d33e2f021f35b83c6a88906426
Author: Jose Pedro M
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : ghc-kinds
http://hackage.haskell.org/trac/ghc/changeset/1684bceaa6a4fed6dab820c36b06336624fa144e
>---
commit 1684bceaa6a4fed6dab820c36b06336624fa144e
Author: Jose Pedro M
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
Branch 'ghc-kinds' now includes:
f8aac1d... Better kind error messages from TcCanonical
3b0e507... Restore file mode
86a2667... Close the handle for the ticker thread (#5604)
17f6f46... add comment noting when we can remove a
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : ghc-kinds
http://hackage.haskell.org/trac/ghc/changeset/62a5be767c0fd5c7a30f95ad6acad21b30ab794d
>---
commit 62a5be767c0fd5c7a30f95ad6acad21b30ab794d
Merge: 72389e7... e9
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/beb183453846286e3218899ebbcf50edbb03ffd6
>---
commit beb183453846286e3218899ebbcf50edbb03ffd6
Author: Jose Pedro Maga
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/e9449158567f44d909c184d0e666ec130978757f
>---
commit e9449158567f44d909c184d0e666ec130978757f
Author: Jose Pedro Maga
| I'm a bit confused about variable shadowing in Core. Since every variable has
a
| Unique I would've thought that there is no problem with that (i.e. a Unique is
| globally unique).
No, as Max says, there is *not* a "no-shadowing" invariant. Shadowing is
allowed.
The Simplifier does generally
| - case = only place evaluation occurs
| - let = only place heap allocation occurs / thunk creation / introduce
laziness
As Simon says, that's not true of Core, only of STG (or Core after CorePrep).
In a application (f e), where is not "trivial" (see CoreUtils.exprIsTrivial),
- the a
On 13/11/2011 01:30, David Terei wrote:
Hi all,
I've seen it said in various places that for Core the semantics are basically:
- case = only place evaluation occurs
- let = only place heap allocation occurs / thunk creation / introduce
laziness
These are both true after the CorePrep phas
New patches in /srv/darcs/git-mirrors/terminfo
commit 64d1e6201b490942636f5f3883cf5e81c2338fc8
Author: Judah Jacobson
Date: Fri Nov 11 17:20:37 2011 +
Fix the termColumns capacity.
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.has
New patches in /srv/darcs/git-mirrors/Cabal
commit 3fd49b380adf2025bd8993b1e8060253d5fa3c91
Author: Duncan Coutts
Date: Fri Nov 11 13:31:13 2011 +
Note in the README that you can install using the cabal program
___
Cvs-ghc mailing list
Cvs-
New patches in /srv/darcs/git-mirrors/bytestring
commit 4bd35121e7ebea7f8df770902027f2ae7ccb4cf8
Author: Duncan Coutts
Date: Sun Nov 13 20:37:41 2011 +
Add Simon's builder benchmark suite and add to .cabal file
Makes use of cabal's new support for benchmarks
commit 992a9433e3047b
simonmar-win32-stable (x86 Windows STABLE), build 377
Build succeeded
Details:
http://darcs.haskell.org/ghcBuilder/builders/simonmar-win32-stable/377.html
git clone| Success
create mk/build.mk | Success
get subrepos | Success
repo versions| Success
setting version d
On 13 November 2011 01:30, David Terei wrote:
> Can anyone confirm that in Core let bindings _aren't_ the only place
> allocation occur (so read it like Haskell) but the 2 rules do hold for
> STG? Or maybe I'm dumping core wrong...
Yep I think you are right - allocation is only confined to "let"
On 13 November 2011 11:28, Michal Terepeta wrote:
> On the other hand it seems that simplifyArgs doesn't exist anymore. So is this
> just a matter of outdated comments or is it actually possible that two
> different
> variables in Core AST will have the same Unique?
The comment about the source
| It would be nice if the compiler could apply SPECIALIZE pragmas
| recursively. For example, if I have a polymorphic function f which calls
| polymorphic functions g and h, it would be nice if one could apply a
| SPECIALIZE pragma to f and have g and h specialized automatically. Just
| a thought.
39 matches
Mail list logo