- 16 May, 2009 4 commits
-
-
Ian Lynagh authored
-
Ian Lynagh authored
-
Ian Lynagh authored
-
Ian Lynagh authored
-
- 15 May, 2009 14 commits
-
-
Ian Lynagh authored
-
Ian Lynagh authored
-
Ian Lynagh authored
-
Ian Lynagh authored
-
Ian Lynagh authored
-
Ian Lynagh authored
It's now in the nofib repo.
-
Ian Lynagh authored
Now configure looks for it as an installed program instead.
-
Simon Marlow authored
I'm less convinced this is a good idea now. But it does avoid rebuilding most of stage1 when you pull and reconfigure. Better solutions welcome.
-
Simon Marlow authored
-
Simon Marlow authored
-
Simon Marlow authored
-
Simon Marlow authored
we also have $1_$2_CONFIGURE_OPTS, which is used.
-
Simon Marlow authored
-
chak@cse.unsw.edu.au. authored
-
- 14 May, 2009 7 commits
-
-
Simon Marlow authored
-
Simon Marlow authored
-
Ian Lynagh authored
-
Ian Lynagh authored
-
Simon Marlow authored
-
Simon Marlow authored
-
Simon Marlow authored
-
- 13 May, 2009 2 commits
-
-
Simon Marlow authored
This fixes build problems of the form ghc-cabal: Version mismatch between ghc and ghc-pkg
-
Simon Marlow authored
-
- 14 May, 2009 1 commit
-
-
Ian Lynagh authored
-
- 13 May, 2009 5 commits
-
-
Ian Lynagh authored
-
Ian Lynagh authored
-
simonpj@microsoft.com authored
A long-standing improvement to the error message for kinds. Now instead of Expected kind `* -> *', but `Int' has kind `*' we get The first argument of `T' should have kind `* -> *', but `Int' has kind `*' Ha!
-
simonpj@microsoft.com authored
Record updates are amazingly hard to typecheck right. This is one place where GHC's policy of typechecking the original source is much harder than desugaring and typechecking that! Anyway, the bug here is that to compute the 'fixed' type variables I was only looking at one constructor rather than all the relevant_cons Test is typecheck/should_compile/T3219, which GHC 6.10 barfs on (with Lint).
-
simonpj@microsoft.com authored
-
- 01 May, 2009 2 commits
-
-
Duncan Coutts authored
When using shared libs we should link each lib against its deps. This allows the dynamic linker to chase dependencies and means we do not have to specify all indirect dependencies (as we must do for static libs).
-
Duncan Coutts authored
As is already the case for ghc -fPIC. This is needed because ghc -dynamic means to generate code that is capable of being linked to Haskell shared libs and for C code the equivalent is -fPIC. Normally C code does not need -fPIC merely to link to shared libs however Haskell shared libs do not follow common conventions. In particular the static data cannot be referenced statically because it cannot be copied by the static linker. The linker cannot copy them because we do not specify a .size for the _closure entries (in the .data section) though in principle we could.
-
- 13 May, 2009 4 commits
-
-
Simon Marlow authored
-
Simon Marlow authored
-
Simon Marlow authored
-
Simon Marlow authored
-
- 22 Apr, 2009 1 commit
-
-
y.zhuang5@lse.ac.uk authored
-