- Glasgow-haskell-users

cross-compiling ghc to openbsd
by Nicolas Martyanoff 30 Jan '10

30 Jan '10

Hi, I'm trying to cross-compile GHC as follows: Host: Linux, x86_64, GHC 6.12.1 Target: OpenBSD 4.6 stable, i386 I follow the guide at: http://hackage.haskell.org/trac/ghc/wiki/Building/Porting I downloaded the last stable source tarball (ghc-6.12.1-src.tar.bz2), then ran the following commands: export AUTOCONF_VERSION=2.62 export AUTOMAKE_VERSION=1.9 cp /bin/pwd utils/ghc-pwd/ghc-pwd sh boot ./configure --enable-hc-boot --build=i386-unknown-openbsd --host=i386-unknown-openbsd --target=i386-unknown-openbsd gmake bootstrapping-files The latest fails, with the following trace: http://pastebin.ca/1770926 The following errors are quite interesting: includes/stg/Types.h:103:2: #error GHC untested on this architecture: sizeof(void *) != 4 or 8 includes/rts/Constants.h:156:2: #error unknown SIZEOF_VOID_P Does someone what's going on with this build ? Is there something I can to to help on these issues ? Regards, -- Nicolas Martyanoff http://codemore.org khaelin(a)gmail.com

4 6

Re: GHC core plugins
by José Pedro Magalhães 29 Jan '10

29 Jan '10

Hi Max, 2010/1/27 Max Bolingbroke <batterseapower(a)hotmail.com> > 2010/1/27 José Pedro Magalhães <jpm(a)cs.uu.nl>: > > Alright, ticket created: http://hackage.haskell.org/trac/ghc/ticket/3843 > > > > In any case, for now I am willing to hard-code a new core-to-core pass on > > the compiler. Any pointers for where I have to look at? > > I recommend you look at compiler/simplCore/CSE.lhs. It is a simple > example of a core-to-core pass. > > However, in short you'll need to: > 1) Create a function which implements your core to core pass, of a > type such as [CoreBind] -> [CoreBind] > *) If that function lives in a new module, edit ghc.cabal.in to tell > the build system about the module > 2) Add a constructor to the CoreToDo data type in > compiler/simplCore/CoreMonad.lhs > 3) Add a case for it to the coreDumpFlag and Outputable instance > 4) Add that pass to the list returned by getCoreToDo in CoreMonad. The > order of the list is the order the passes will be run in. > *) If you want the pass to be under the control of a new flag, you'll > need to add a new dynflag - add a constructor to the DOpt data type in > compiler/main/DynFlags.lhs, and add something to build that > constructor to one of the lists that get fed to the command line > handling code in the same module. It should be fairly obvious how to > do this. > 5) Add a handler for the new constructor to > compiler/simplCore/SimplCore.lhs, in the doCorePass function which > calls into the core pass function you wrote > > Hope that helps, > Max > Yes, that helped quite a lot. One last thing: currently it takes me about 6 minutes to rebuild the compiler after I change the core pass. Are there any tricks of the build system I can use to speed this up? I'm already using a fast build without optimizations and docs... Thanks, Pedro

3 3

bug in template haskell (with recursion?)
by Jake Wheat 28 Jan '10

28 Jan '10

Hello All, I'm trying to write a splice to make HList type signatures a bit more concise, I don't know whether this is a good idea or not. I wrote a small function to do '[(Type,Type)] -> Q Type' for this, and got the following from GHC. Should I add this to the bug tracker? Details: THBug1.hs: {-# LANGUAGE TemplateHaskell #-} module THBug1 where import Data.HList import Language.Haskell.TH mhlt :: [(Type,Type)] -> Q Type mhlt x = [t| Record $(foldThing x)|] where foldThing ((f,t):xs) = [t|HCons (LVPair (Proxy $f) $t) $(foldThing xs)|] foldThing [] = [t|HNil|] ---- $ ghc -c THBug1.hs THBug1.hs:12:61: GHC internal error: `foldThing' is not in scope during type checking, but it passed the renamer tcg_type_env of environment: [] In the expression: foldThing xs In the Template Haskell quotation [t| HCons (LVPair (Proxy $f) $t) $(foldThing xs) |] In the expression: [t| HCons (LVPair (Proxy $f) $t) $(foldThing xs) |] I'm using GHC 6.12.1 from debian experimental: $ ghc --version The Glorious Glasgow Haskell Compilation System, version 6.12.1 $ ghc-pkg list |grep template template-haskell-2.4.0.0 To get HList to install with GHC 6.12, I downloaded the latest version from http://old-darcs.well-typed.com/HList/ and altered it slightly, updated package here: http://launchpad.net/hssqlppp/prealpha/environment/+download/HList-0.2.tar.… the changes I made are: diff -rN old-HList/Data/HList/GhcSyntax.hs new-HList/Data/HList/GhcSyntax.hs 2c2 < {-# LANGUAGE FlexibleContexts #-} --- > {-# LANGUAGE FlexibleContexts, TypeOperators #-} diff -rN old-HList/Data/HList/Label2.hs new-HList/Data/HList/Label2.hs 1c1,2 < {-# LANGUAGE FlexibleInstances, MultiParamTypeClasses, UndecidableInstances, EmptyDataDecls #-} --- > {-# LANGUAGE FlexibleInstances, MultiParamTypeClasses, UndecidableInstances, EmptyDataDecls, > ExistentialQuantification #-} 36c37 < data HNat x => Label x ns desc -- labels are exclusively type-level entities --- > data Label x ns desc = HNat x => Label x ns desc -- labels are exclusively type-level entities diff -rN old-HList/Data/HList/Label3.hs new-HList/Data/HList/Label3.hs 1c1,2 < {-# LANGUAGE FlexibleInstances, MultiParamTypeClasses, UndecidableInstances, EmptyDataDecls #-} --- > {-# LANGUAGE FlexibleInstances, MultiParamTypeClasses, UndecidableInstances, EmptyDataDecls, > ExistentialQuantification #-} 37c38 < data HNat x => Label x ns desc -- labels are exclusively type-level entities --- > data Label x ns desc = HNat x => Label x ns desc -- labels are exclusively type-level entities (If it's not obvious, I have no idea what I'm doing..., but my small amount of code which uses HList worked fine with this altered package.) Thanks, Jake Wheat

1 1

tracing messages
by Serge D. Mechveliani 28 Jan '10

28 Jan '10

Dear GHC team, this is on tracing in ghc-6.12.1 (made from source on Debian Linux i-386-like machine). I wonder what is the reason for this tracing message (starting with `Step1 ...' ): ---------------------------- ... equations calc = [j < i -> true, m <= p -> true, p <= q -> true, q <= n -> true, (A p) <= (A q) -> false, (X <= Y) | (Y < X) -> true, | {not (Y <= n), not (m <= X), not (X < i), not (j < Y), (A X) <= (A Y)} -> true, | {not (X <= Y), not (Y <= j), not (m <= X), (A X) <= (A Y)} -> true, | {not (XStep 1. Starting mutual pre-reduction. The number of rules is 25. Pre-reduction done. Initial numbers of equations is 9, after reduction: 9, the pre-reduction cost is 484. ... ... ---------------------------- The main program does the following in succession: 1) finds eqs, 2) prints "equations calc =\n", shows eqs "\n\n", "Starting completion.\n", "remaining goals = ", 3) finds res by completion (`complete'), 4) prints shows (completionGoalRem res) "\n" The trace calls are set only in the function `complete'. The above message Step 1. Starting mutual pre-reduction. The number of rules is 25. Pre-reduction done. Initial numbers of equations is 9, occurs the first message of this tracing. But the main program must have printed the full last equation in eqs, and only after this any tracing message could appear. Instead, it breaks the last equation printing with the tracing messages. The further evaluation is long, so I interrupted it, without seeing the final result. But this printing break looks strange, because eqs does not depend on the results of `complete', the reverse holds: the latter applies to eqs. Generally, I often observe an effect of this kind; it is harmless, but I wonder, what might be the reason. Regards, ----------------- Serge Mechveliani mechvel(a)botik.ru

2 2

FW: GHC core plugins
by Simon Peyton-Jones 28 Jan '10

28 Jan '10

-----Original Message----- From: Simon Peyton-Jones Sent: 28 January 2010 07:50 To: 'austin s' Subject: RE: GHC core plugins compiler/cmm/ZipDataFlow.hs But we have great ideas for making it much simpler and more modular. In progress.. S | -----Original Message----- | From: mad.one(a)gmail.com [mailto:mad.one@gmail.com] On Behalf Of austin s | Sent: 27 January 2010 16:24 | To: Simon Peyton-Jones | Subject: Re: GHC core plugins | | 2010/1/27 Simon Peyton-Jones <simonpj(a)microsoft.com>: | > | Also, is Hoopl expected to be used on core -> core plugins, and, if so, | is | > | the | > | infrastructure in place for this? | > | > no, Hoopl works on imperative control flow graphs, the C-- part of the back | end, not on Core. | > | > Simon | > _______________________________________________ | > Glasgow-haskell-users mailing list | > Glasgow-haskell-users(a)haskell.org | > http://www.haskell.org/mailman/listinfo/glasgow-haskell-users | > | | Quick Question, even if it is OT: Is the Hoopl code available anywhere? | | -- | - Austin

1 0

Re: GHC core plugins
by austin s 27 Jan '10

27 Jan '10

On Wed, Jan 27, 2010 at 10:24 AM, austin s <as(a)nijoruj.org> wrote: > 2010/1/27 Simon Peyton-Jones <simonpj(a)microsoft.com>: >> | Also, is Hoopl expected to be used on core -> core plugins, and, if so, is >> | the >> | infrastructure in place for this? >> >> no, Hoopl works on imperative control flow graphs, the C-- part of the back end, not on Core. >> >> Simon >> _______________________________________________ >> Glasgow-haskell-users mailing list >> Glasgow-haskell-users(a)haskell.org >> http://www.haskell.org/mailman/listinfo/glasgow-haskell-users >> > > Quick Question, even if it is OT: Is the Hoopl code available anywhere? > > -- > - Austin > Whoops, forgot to add g-h-u to the to: field. ;) -- - Austin

1 0

GHC core plugins
by José Pedro Magalhães 27 Jan '10

27 Jan '10

Hello all, What's the current status of GHC plugins [1] in HEAD? Can I use them? If not, what's the easiest way to add another core-to-core pass to the compiler? Thanks, Pedro [1] http://hackage.haskell.org/trac/ghc/wiki/Plugins

5 6

GHC core plugins
by Max Bolingbroke 27 Jan '10

27 Jan '10

2010/1/27 José Pedro Magalhães <jpm(a)cs.uu.nl>: > Alright, ticket created: http://hackage.haskell.org/trac/ghc/ticket/3843 > > In any case, for now I am willing to hard-code a new core-to-core pass on > the compiler. Any pointers for where I have to look at? I recommend you look at compiler/simplCore/CSE.lhs. It is a simple example of a core-to-core pass. However, in short you'll need to: 1) Create a function which implements your core to core pass, of a type such as [CoreBind] -> [CoreBind] *) If that function lives in a new module, edit ghc.cabal.in to tell the build system about the module 2) Add a constructor to the CoreToDo data type in compiler/simplCore/CoreMonad.lhs 3) Add a case for it to the coreDumpFlag and Outputable instance 4) Add that pass to the list returned by getCoreToDo in CoreMonad. The order of the list is the order the passes will be run in. *) If you want the pass to be under the control of a new flag, you'll need to add a new dynflag - add a constructor to the DOpt data type in compiler/main/DynFlags.lhs, and add something to build that constructor to one of the lists that get fed to the command line handling code in the same module. It should be fairly obvious how to do this. 5) Add a handler for the new constructor to compiler/simplCore/SimplCore.lhs, in the doCorePass function which calls into the core pass function you wrote Hope that helps, Max

1 0

No more ExitException?
by Volker Wysk 27 Jan '10

27 Jan '10

Hello I'm porting my HsShellScript library from GHC-6.8 to GHC-6.10. I'm catching an ExitException in the old version. The only occurence of ExitException in the GHC 6.10 libraries is in Control.OldException. So how is this done in GHC 6.10+ ? What replaces the old ExitException? Cheers, Volker -- Volker Wysk <vw(a)volker-wysk.de>

2 2

Splicing types.. should this work?
by Robert Greayer 25 Jan '10

25 Jan '10

Now that type-splicing works in TH, and TH has type-family support, I was wondering if the following example should compile (with 6.12.1): > {-# LANGUAGE TemplateHaskell, MultiParamTypeClasses, TypeFamilies, > FlexibleInstances, OverlappingInstances #-} > module Sample where > import Control.Monad > import Language.Haskell.TH > class Foo a where > type FooType a > createInstance :: Q Type -> Q Dec > createInstance t = instanceD (return []) > (conT ''Foo `appT` t) [ > tySynInstD ''FooType [t] (conT ''String) > ] > createInstance' :: Q Type -> Q Dec > createInstance' t = liftM head [d| > instance Foo $t where > type FooType $t = String|] the function 'createInstance' compiles without a problem, but it's (near) equivalent written using TH quotations + splices fails with the error: Sample.lhs:22:10: Type indexes must match class instance head Found `t_aMn' but expected `t_aMl' In the associated type instance for `FooType' In the instance declaration for `Foo $t' In the Template Haskell quotation [d| instance Foo $t where type instance FooType $t = String |] The compiler seems to not be able to determine that the type spliced in the class instance head will match the type spliced in the type instance. The first version works fine for my purposes, but was curious whether the failure of the 2nd was a bug or a feature. Thanks, Rob

1 0