Re: Status and future of the LLVM backend

2014-12-27 Thread Erik de Castro Lopo
Ben Gamari wrote: > I've written down some thoughts on the current status and future > direction of the LLVM backend here [1]. Have a look when you get a chance. > > To summarize, > > * it seems like LLVM 3.4 chokes on the code produced by my 3.5 rework > when the `$def` symbols are marked

GHC 7.10.x migration guide

2014-12-27 Thread Herbert Valerio Riedel
Hello! I've started collecting the most common compile-errors (and their respective fixes) I have encountered while compiling Hackage packages with GHC 7.10 in https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10 Feel free to contribute to this migration guide. HTH, hvr

Re: ANNOUNCE: GHC 7.10.1 Release Candidate 1

2014-12-27 Thread Edward Z. Yang
Hello lonetiger, I don't think any relevant logic changed in 7.10; however, this commit may be relevant: commit 8fb03bfd768ea0d5c666bbe07a50cb05214bbe92 Author: Ian Lynagh Sun Mar 18 11:42:31 2012 Committer: Ian Lynagh Sun Mar 18 11:42:31 2012 Original File: compiler

Re: ANNOUNCE: GHC 7.10.1 Release Candidate 1

2014-12-27 Thread Tamar Christina
Hi Edward, You’re right, this is my mistake, I am compiling x86_64 Windows, I have not updated my tools to work on it yet so I’ve been using the x86_32 binaries and didn’t noticed that my msys2 was compiling a 64bit version. That explains the warning, sorry for the false alarm! Regards, Ta

Re: ANNOUNCE: GHC 7.10.1 Release Candidate 1

2014-12-27 Thread cg
*From:* Austin Seipp *Sent:* ‎Tuesday‎, ‎December‎ ‎23‎, ‎2014 ‎15‎:‎36 *To:* ghc-devs@haskell.org , glasgow-haskell-us...@haskell.org We are pleased to announce the first release candidate for

Re: ANNOUNCE: GHC 7.10.1 Release Candidate 1

2014-12-27 Thread Herbert Valerio Riedel
On 2014-12-28 at 04:41:45 +0100, cg wrote: [...] > Besides downloading a tarball, can I checkout it using git? > > I tried using sync-all as described on wiki [1] to checkout it: > > ./sync-all checkout ghc-7.10 > > but it seems it doesn't work, there are error message like: > error: pathspec 'gh