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 Sat May 14 18:10:01 BST 2011.
checking out new source tree
pgj-freebsd-amd64-stable (amd64 FreeBSD STABLE), build 242
Build failed
Details:
http://darcs.haskell.org/ghcBuilder/builders/pgj-freebsd-amd64-stable/242.html
git clone| Success
create mk/build.mk | Success
get subrepos | Success
setting version date | Success
booting
pgj-freebsd-i386-stable (x86 FreeBSD STABLE), build 225
Build failed
Details:
http://darcs.haskell.org/ghcBuilder/builders/pgj-freebsd-i386-stable/225.html
git clone| Success
create mk/build.mk | Success
get subrepos | Success
setting version date | Success
booting
pgj2 (amd64 FreeBSD HEAD), build 360
Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/pgj2/360.html
git clone| Success
create mk/build.mk | Success
get subrepos | Success
setting version date | Success
booting | Success
configuring | S
pgj (x86 FreeBSD HEAD), build 362
Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/pgj/362.html
git clone| Success
create mk/build.mk | Success
get subrepos | Success
setting version date | Success
booting | Success
configuring | Succe
tn23 (x86 OSX HEAD), build 338
Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/tn23/338.html
git clone | Success
create mk/build.mk | Success
get subrepos | Failure: Just (ExitFailure 2)
Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/tn23/338
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 Sat May 14 18:10:01 BST 2011.
checking out new s
On 11 May 2011 13:36, Max Bolingbroke wrote:
> I thought you were arguing against choice 1 and in favour of 2 in your
> initial message?
I've pushed my implementation pretty much as it was at the beginning
of this thread to master so it can go into 7.2. Please let me know of
any problems you enco
kgardas-opensolaris-x86-head (x86 Solaris HEAD), build 232
Build failed
Details:
http://darcs.haskell.org/ghcBuilder/builders/kgardas-opensolaris-x86-head/232.html
git clone | Success
create mk/build.mk | Success
get subrepos | Failure: Just (ExitFailure 2)
Build failed
Details:
Hello all,
I've just pinned down a nasty bug in the new code generator (not my code,
whoo!) that was tickled by my aggressive optimization pass. In the old
code generator (CgUtils.hs), we have the following section for caller saves:
callerSaves :: GlobalReg -> Bool
#ifdef CALLER_SAVES_B
sparky-unreg (Sparc Solaris unreg HEAD), build 120
Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/sparky-unreg/120.html
git clone | Failure: Just (ExitFailure 9)
Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/sparky-unreg/120.html
ld.so.1: git: fatal: rel
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 Sat May 14 18:00:01 BST 2011.
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 Sat May 14 18:00:01 BST 2011.
checking out new source
Oh yeah, sorry ^_^
Columns:
1. Percent size change of binary
2. Size of the old binary
3. Delta between old binary and new binary
Where "old" is "compiled with old codegen" and vice versa.
Thus,
> 0.2699 7024 1896 ./stranal/should_run/strun001.o
means that strun001.o was 7kb when compile
I spent some time last evening and today fixing some more low
hanging fruit (still waiting for a big enough chunk of free time to
tackle the spill and stack layout rewrites), and here are the latest
statistics:
0.2558 5160 1320 ./deSugar/should_compile/ds018.o
0.2565 7204 1848 ./ga
Currently, -ddump-to-file appends to an existing file. This is pretty confusing
for me, if I wanted to get a new set of information, because now I have to
delete
any dump files before I take more data, or I need to manually separate out the
runs (which, by the way, are not demarcated.)
If no one
It's tough to tell with just the commit log. Can you pop open gitk and take a
look? (maybe
take a screen shot and share.)
Edward
Excerpts from Ben Lippmeier's message of Sat May 14 04:37:09 -0400 2011:
>
> On 13/05/2011, at 8:56 PM, Edward Z. Yang wrote:
>
> > Hey Ben,
> >
> > It looks like y
On 13/05/2011, at 8:56 PM, Edward Z. Yang wrote:
> Hey Ben,
>
> It looks like you broke the build for other people in
> 5bfa6a6382a4e4b949d333b1996065e9bcfacb18.
Urgh, sorry. It looks like I tripped over an #ifdef mine. I tried to validate
Erik's patch just now but I've messed up my git repo
18 matches
Mail list logo