pgj (x86 FreeBSD HEAD), build 891
Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/pgj/891.html
git clone| Success
create mk/build.mk | Success
get subrepos | Success
repo versions| Success
touching clean-check files
Build description = STABLE on i386-unknown-linux (cam-02-unx)
Build location= /playpen/simonmar/nightly/STABLE
Build config file = /home/simonmar/nightly/site/msrc/conf-STABLE-cam-02-unx
Nightly build started on cam-02-unx at Tue Dec 18 18:10:02 GMT 2012.
checking out new source tree
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 Tue Dec 18 18:00:01 GMT 2012.
checking out new source
tn23 (x86 OSX HEAD), build 785
Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/tn23/785.html
git clone| Success
create mk/build.mk | Success
get subrepos | Success
repo versions| Success
touching clean-check files
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 Tue Dec 18 18:10:01 GMT 2012.
checking out new s
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/909d52e20405bf18b5fb337e64318112bb553cd8
>---
commit 909d52e20405bf18b5fb337e64318112bb553cd8
Author: Iavor S. Diatch
So first, IIUC, the dependency on GHCi
is incidental, but the dependency on dynamic loading and the
linker (which is currently part of GHCi) isn't. Plugins without
bootstrapping may be possible, but seem a likely fiddly business.
I know currently plu
Build description = HEAD (unreg) on x86_64-unknown-linux (cam-04-unx)
Build location= /64playpen/simonmar/nightly/HEAD-unreg-cam-04-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-unreg-cam-04-unx
Nightly build started on cam-04-unx at Tue Dec 18 18:20:01 GMT 2012.
chec
Build description = HEAD on i386-unknown-linux (cam-02-unx)
Build location= /playpen/simonmar/nightly/HEAD
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx
Nightly build started on cam-02-unx at Tue Dec 18 18:00:02 GMT 2012.
checking out new source tree
On Mon, Dec 17, 2012 at 02:01:28PM +, Simon Peyton-Jones wrote:
> | On Mon, Dec 17, 2012 at 09:21:44AM +, Simon Peyton-Jones wrote:
> | >
> | > o There's a seg-fault
> |
> | I can reproduce this. I'll look into it.
>
> Great, thank you.
>
> It turns out that simply
>
> ghc-stage
Ok with me too. I should have cleaned this up at the time, but got into
the habit of using -ddump-cmmz.
Cheers,
Simon
On 17/12/12 21:46, Simon Peyton-Jones wrote:
ok with me
| -Original Message-
| From: cvs-ghc-boun...@haskell.org [mailto:cvs-ghc-boun...@haskell.org] On
|
On 18/12/12 12:33, Roman Cheplyaka wrote:
* Simon Peyton-Jones [2012-12-18 10:32:39+]
(This belongs on cvs-ghc, or the upcoming ghc-devs.)
| I find our tests to be quite hard to navigate, as the majority have
| names like tc12345.hs or some such. I suggest we instead use descriptive
| name
Repository : ssh://darcs.haskell.org//srv/darcs/testsuite
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/9f4dd2d2235aaa4bb3965c0752775ad309c2fafb
>---
commit 9f4dd2d2235aaa4bb3965c0752775ad309c2fafb
Author: Johan Tib
On 2012-12-18 13:33, Roman Cheplyaka wrote:
But I wonder what if one wants to create a test preventively (say,
for a
new feature), and there isn't actually any bug to create a ticket
for?
Roman
In that case, I would open a ticket with the type 'feature request' to
get the right ticket numb
| But I wonder what if one wants to create a test preventively (say, for a
| new feature), and there isn't actually any bug to create a ticket for?
Create a ticket for the new feature!
Simon
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.hask
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/55c55f141b8b312512cce1d7e0fbd3a8088de964
>---
commit 55c55f141b8b312512cce1d7e0fbd3a8088de964
Author: Simon Marlow
D
Repository : ssh://darcs.haskell.org//srv/darcs/ghc
On branch : master
http://hackage.haskell.org/trac/ghc/changeset/a006ecdfd381fa75ab16ddb66c3a2b247f359eb8
>---
commit a006ecdfd381fa75ab16ddb66c3a2b247f359eb8
Author: Simon Marlow
D
On Tue, Dec 18, 2012 at 2:32 AM, Simon Peyton-Jones
wrote:
> OK? We should document this convention somewhere.
As long as this is the policy nowadays I don't feel a strong need to
document it, but feel free to if you want.
___
Cvs-ghc mailing list
Cvs
(This belongs on cvs-ghc, or the upcoming ghc-devs.)
| I find our tests to be quite hard to navigate, as the majority have
| names like tc12345.hs or some such. I suggest we instead use descriptive
| names like GADT.hs or PrimOps.hs instead. What do people think?
We've really moved to a naming co
Looks good.
Edward
Excerpts from Austin Seipp's message of Tue Dec 18 01:34:44 +0800 2012:
> Hi,
>
> The attached patch renames the various '*-cmmz-*' flags to '*-cmm-*'
> now that the new backend is live. It also fixes some inconsistencies;
> namely, there were flags like -ddump-cmmz-rewrite, v
pgj-freebsd-amd64-stable (amd64 FreeBSD STABLE), build 765
Build succeeded
Details:
http://darcs.haskell.org/ghcBuilder/builders/pgj-freebsd-amd64-stable/765.html
git clone| Success
create mk/build.mk | Success
get subrepos | Success
repo versions
Austin is dead right. In principle you could compile a plug-in with the exact
same compiler (not just version but which build was used) as the one used to
build stage-1. But that's delicate and we've never thought about it, so I
doubt the other ancillary things Austin mentions would work.
Sorr
22 matches
Mail list logo
