RE: Dynamic Programming with Memoizing

2006-04-29 Thread Simon Peyton-Jones
You don't want (map q' (range dom)) to be computed for each call of q, do you. To make GHC realise that this expression does not depend on the arguments, you need the full laziness transformation, which you get with -0. GHCi doesn't use -O, though. So do this ghc -c Foo.hs -O

Building ghc-6.4 on Solaris x86

2006-04-29 Thread Georg Sauthoff
Hi, I am trying to build ghc-6.4.2 under solaris x86 (10.0). I mainly followed http://www.haskell.org/ghc/docs/latest/html/building/sec-porting-ghc.html, but now I am stuck. I managed to build an unregistered ghc at the target. I build the .hc files on a x86 Linux box. It compiles hello world

Re: Building ghc-6.4 on Solaris x86

2006-04-29 Thread Georg Sauthoff
Hi, I forgot one thing: at the solaris x86 system is a ghc-6.2 already installed. Via start script it uses -fvia-C. So building 6.4.2 with it give me a different error: # PATH=/var/tmp/gsauthof/bin:/usr/sfw/bin:$PATH ./configure --with-gcc=/usr/sfw/bin/gcc --with-ghc=/vol/ghc-6.2/bin/ghc

Re: Building ghc-6.4 on Solaris x86

2006-04-29 Thread Einar Karttunen
On 29.04 17:47, Georg Sauthoff wrote: Hi, I am trying to build ghc-6.4.2 under solaris x86 (10.0). Hello A few months ago physrules ported GHC 6.4.1 to solaris x86. There were a few problems (and the tarball does not have the install target fixed), but the binary should work. Hopefully this

Re: WordPtr,IntPtr,IntMax,WordMax

2006-04-29 Thread Manuel M T Chakravarty
Am Donnerstag, den 06.04.2006, 16:37 -0700 schrieb John Meacham: On Thu, Apr 06, 2006 at 04:28:01PM -0700, John Meacham wrote: I was curious if ghc could support the following basic types, they will likely just be aliases of existing types. WordPtr uintptr_t WordMax uintmax_t IntPtr

Re: ANNOUNCE: GHC vesrion 6.4.2

2006-04-29 Thread Isaac Jones
Some more bad news... The Cabal hooks interface from 6.4.2 is pretty different from the current darcs head. The differences were to make things more consistent and less likely to change in the future. I can't see really going back to the version that's in 6.4.2. I fear that'll make the problem