Hi,
I'm interested in looking at the effects on performance of various
compiler optimizations in GHC. I ran the nofib benchmarks against the
stable branch to get a feel for some very simple results. In my
measurements I only saw a maximum of 2.8% difference in runtime when
using -O0 and -
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 Thu Oct 8 19:00:01 BST 2009.
***
Thu Oct 8 08:34:12 PDT 2009 Ian Lynagh
* Remove FP_MINGW_GCC now that we use an in-tree gcc
M ./aclocal.m4 -14
M ./configure.ac -1
View patch online:
http://darcs.haskell.org/ghc/_darcs/patches/20091008153412-3fd76-a4d85ff907cfb346acfec76f6158731ff27b2597.gz
Thu Oct 8 08:32:44 PDT 2009 Ian Lynagh
* Remove the windres configure check, now that we use an in-tree windres
M ./aclocal.m4 -39
M ./configure.ac -3
View patch online:
http://darcs.haskell.org/ghc/_darcs/patches/20091008153244-3fd76-0031a23089db1af91ebd59b379faba4058e7efe7.gz
Thu Oct 8 08:10:45 PDT 2009 Ian Lynagh
* Fix configure on non-Windows
M ./configure.ac -1 +1
View patch online:
http://darcs.haskell.org/ghc/_darcs/patches/20091008151045-3fd76-1c7afcc1ecdce035948a18eca80f696a9773f123.gz
___
Cvs-ghc mailing li
Thu Oct 8 08:03:45 PDT 2009 Ian Lynagh
* Refactor configure to fix building on msys
M ./aclocal.m4 -36 +2
M ./configure.ac -35 +48
View patch online:
http://darcs.haskell.org/ghc/_darcs/patches/20091008150345-3fd76-5def748ac21ba969afa485a95889944708d229ca.gz
On Thu, Oct 08, 2009 at 03:58:40PM +0100, Duncan Coutts wrote:
>
> Ian will need to hasten the switch over from the tarball back to the
> repo before this warning becomes fatal.
Or you could make a .1 release, and we can update to that tarball.
> I think he was hoping to do that
> slowly so that
On Thu, 2009-10-08 at 13:11 +, Simon Peyton-Jones wrote:
> Duncan, Don
>
> GHC will soon start warning about redundant SPECIALISE pragmas. A few
> weeks ago, I mentioned that bytestring has two such examples. Could
> you remove them from the upstream bytestring, please? Otherwise we
> won't
Duncan, Don
GHC will soon start warning about redundant SPECIALISE pragmas. A few weeks
ago, I mentioned that bytestring has two such examples. Could you remove them
from the upstream bytestring, please? Otherwise we won't be able to validate.
Thanks
libraries/bytestring/Data/ByteString/In
Build description = HEAD on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
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 Wed Oct 7 18:00:01 BST 2009.
checking out
Build results:
x86-64 Linux head: pass
x86 Windows head fast: pass pass
sparky head: pass
x86-64 Linux head unreg: pass
Old unexpected test passes:
length001 1 tnaur x86 OS X head
unicode001 1 kili head
unicode002 1 kili head
Fixed unexpected test failures:
Build results:
kgardas stable: fail (failed boot)
tnaur PPC OSX stable 2: fail (failed compile)
tnaur x86 OS X stable: pass
x86 Linux stable:pass
x86 Windows stable fast: pass pass
x86-64 Linux stable: pass
Old unexpected test passes:
length001 1 tnaur x86 OS X stabl
12 matches
Mail list logo