Mon Oct 6 17:44:16 PDT 2008 Roman Leshchinskiy <[EMAIL PROTECTED]>
* Add Word8 support to vectoriser
MERGE TO 6.10
M ./compiler/vectorise/VectBuiltIn.hs -4 +20
View patch online:
http://darcs.haskell.org/ghc/_darcs/patches/20081007004416-b2b0a-57af3e714e86f885a112df00219e43335cab9878
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 Mon Oct 6 18:02:06 BST 2008.
checking out
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 Oct 6 19:00:01 BST 2008.
***
2008/10/4 Thomas Schilling <[EMAIL PROTECTED]>:
> 'loadModule' now takes a ModSummary which should be enough to emulate
> checkAndLoadModule with the new API. It's in head and should be in
> stable soon.
So how do I use this? Can you paste a snippet of code that, given a
list of files (or module
Claus Reinke wrote:
Is it really always safe to combine packages that depend on one base
with packages that depend on another? My guess is "no, but ghc will
catch any compatibility issues", so the cabal warning perhaps
shouldn't be dropped?
As far as I can see the answer is yes but I'd be int
Claus Reinke wrote:
-- pretend we're loading a package that depends on base 3 into a
-- session that otherwise depends on base 4
$ ./ghc-6.11.20081004/bin/ghcii.sh -package base-3.0.3.0
-ignore-dot-ghci
..
Prelude> :m +Data.Generics.Basics
Could not find module `Data.Generics.Basics':
it was f
-- pretend we're loading a package that depends on base 3 into a
-- session that otherwise depends on base 4
$ ./ghc-6.11.20081004/bin/ghcii.sh -package base-3.0.3.0 -ignore-dot-ghci
..
Prelude> :m +Data.Generics.Basics
Could not find module `Data.Generics.Basics':
it was found in multiple packag
Is it really always safe to combine packages that depend on one base
with packages that depend on another? My guess is "no, but ghc will
catch any compatibility issues", so the cabal warning perhaps shouldn't
be dropped?
As far as I can see the answer is yes but I'd be interested to see a
coun
Claus Reinke wrote:
Sometimes, when I cc emails to those who might be particularly
interested, or able to do something about the issues discussed, I
notice that the email arrives in the list without the cc.
Example: the email with the subject "base 3 + base 4 compatibility?"
was cc-ed to 3 addre
Claus Reinke wrote:
Is it really always safe to combine packages that depend on one base
with packages that depend on another? My guess is "no, but ghc will
catch any compatibility issues", so the cabal warning perhaps shouldn't
be dropped? Either way, safe does not mean useable, eg, how does o
Hi Don
Did you make any progress with those three specialisation bugs?
Simon
| -Original Message-
| From: [EMAIL PROTECTED] [mailto:glasgow-haskell-bugs-
| [EMAIL PROTECTED] On Behalf Of GHC
| Sent: 04 October 2008 12:55
| Cc: [EMAIL PROTECTED]
| Subject: Re: [GHC] #1434: Slow conversion
Duncan Coutts wrote:
On Sun, 2008-10-05 at 00:35 +0100, Thomas Schilling wrote:
2008/10/4 Duncan Coutts <[EMAIL PROTECTED]>:
all people who use the ghc-6.10 branch darcs
repos deleting their libraries/bytestring repo and getting the new one.
How is that different from having to call ./darcs-al
Build results:
x86-64 Linux head: lost
x86 Windows head:pass
x86 Windows head fast: pass pass pass pass pass fail (failed stage1)
macgyver PPC OSX head: fail (failed getsubrepos)
tnaur x86 Linux head:pass
x86-64 Linux head unreg: lost
New unexpected test failures:
conc04
Build results:
kgardas stable: pass
macgyver PPC OSX stable:fail (failed darcs)
malcolm stable: pass
mnemosyne x86-64 Gentoo stable: fail (failed darcs)
x86 Windows stable: pass
x86 Windows stable fast:pass pass pass pass fail (failed stag
14 matches
Mail list logo