[nightly] 18-Jan-2010 build of HEAD on x86_64-unknown-linux (cam-04-unx.europe.corp.microsoft.com)

2010-01-18 Thread GHC Build Reports
Build description = HEAD on x86_64-unknown-linux (cam-04-unx.europe.corp.microsoft.com) 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 Jan 18 19:00:01 GMT 2010. **

patch applied (ghc-6.12/ghc): Update some comments about how autoconf/configure works

2010-01-18 Thread Ian Lynagh
Mon Jan 18 06:59:59 PST 2010 Ian Lynagh * Update some comments about how autoconf/configure works M ./mk/install.mk.in -5 +2 View patch online: http://darcs.haskell.org/ghc-6.12/ghc/_darcs/patches/20100118145959-3fd76-2f77752aab04c424181465b608742664fc3c7044.gz __

patch applied (ghc-6.12/ghc): Rolling back: Make FastString thread-safe.

2010-01-18 Thread Ian Lynagh
Thu Dec 31 08:46:51 PST 2009 Simon Marlow * Rolling back: Make FastString thread-safe. This patch was the cause of the compile-time performance regression in #3796. My guess is that it is due to the use of unsafePerformIO which traverses the stack up to the first update frame, and

Re: hpc bug lurking?

2010-01-18 Thread Andy Gill
Your patch looks completely reasonable, and you should apply it. Using Int was plain wrong, it should be Int32. Andy On Jan 14, 2010, at 12:00 PM, Tristan Allwood wrote: Hi, In short: I think data ModuleInfo = ModuleInfo String Int Hash (Ptr Word64) in Trace.HPC.Reflect should be data Mod

patch applied (ghc): Update some comments about how autoconf/configure works

2010-01-18 Thread Ian Lynagh
Mon Jan 18 06:59:59 PST 2010 Ian Lynagh * Update some comments about how autoconf/configure works M ./mk/install.mk.in -5 +2 View patch online: http://darcs.haskell.org/ghc/_darcs/patches/20100118145959-3fd76-2f77752aab04c424181465b608742664fc3c7044.gz ___

patch applied (ghc): Fix a warning message

2010-01-18 Thread Ian Lynagh
Mon Jan 18 06:20:20 PST 2010 Ian Lynagh * Fix a warning message We were printing the wrong value, so getting confusing messages like: Function `$wa{v s17LO} [lid]' has 2 call pattterns, but the limit is 3 M ./compiler/specialise/SpecConstr.lhs -3 +2 View patch online: ht

Daily report for head

2010-01-18 Thread BuildBot Collator
Build results: Dropping unexpected test passes reports from builders not seen in 7 days: x86 Windows head fast Dropping unexpected test failures reports from builders not seen in 7 days: x86 Windows head fast Fixed unexpected test failures: hsc2hs001 hsc2hs002 ___

Daily report for stable

2010-01-18 Thread BuildBot Collator
Build results: Dropping unexpected test passes reports from builders not seen in 7 days: x86 Windows stable fast Dropping unexpected test failures reports from builders not seen in 7 days: x86 Windows stable fast Fixed unexpected test failures: T1969 break024 outofmem2