Hi,
I just got ghc7 and compiled with ghc6.12.1 and default configuration.
ghc works fine. So I tried to use llvm. I got:
ghc -fllvm badge.hs
[1 of 1] Compiling Main ( badge.hs, /tmp/Main.o )
opt: Bitcode stream should be a multiple of 4 bytes in length
I am using debian 32bit sys
| known problem with darcs with no obvious solution. For me, switching
| GHC to git would certainly be a win.
I have personal experience of git, because I co-author papers with git users. I
am not very technologically savvy, but my failure rate with git is close to
100%. Ie I can do the equiva
On 8 December 2010 08:28, Magicloud Magiclouds
wrote:
> I am using debian 32bit system, llvm 2.6.
I haven't seen your particular error before, but AFAIK -fllvm won't
work with LLVM < 2.7 because it depends on the GHC calling convention
that is only present from that release onwards. Try upgradin
I like Git for Computer Scientists [1] and Git in pictures [2]. It also
sounds like a Git for Darcs users might be in order.
Edward
[1] http://eagain.net/articles/git-for-computer-scientists/
[2] http://blog.nelhage.com/2010/01/git-in-pictures/
___
Gl
On Wed, Dec 8, 2010 at 12:31 PM, Edward Z. Yang wrote:
> I like Git for Computer Scientists [1] and Git in pictures [2]. It also
> sounds like a Git for Darcs users might be in order.
Once you got the general ideas down I'd recommend
http://nvie.com/posts/a-successful-git-branching-model/
I did a bit more merging of your branch. My current state is here:
http://darcs.haskell.org/ghc-cmm-15Sep10/
it doesn't actually build, but the failure is somewhere in hoopl I
think. This branch is 400-odd patches behind the current HEAD. I don't
think I borked anything too badly during the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/8/10 03:45 , Simon Peyton-Jones wrote:
> | known problem with darcs with no obvious solution. For me, switching
> | GHC to git would certainly be a win.
>
> I have personal experience of git, because I co-author papers with git users.
> I am n
On Dec 8, 2010, at 2:45 AM, Simon Peyton-Jones wrote:
> If anyone has a favourite "how to understand git" doc, do point me at it.
You may have already tried these, but I've found the [official git tutorial][1]
to be pretty decent. The [second part][2] contains some details on how git sees
the
Iavor Diatchki wrote:
> I use git for a lot of my development...
> Given the responses though, it sounds like this is a well
> known problem with darcs with no obvious solution.
Why do you say there is no obvious solution? In fact, Ganesh,
representing the Darcs team, responded:
>> 1) a darcs reb
Yitzchak Gale wrote:
> Iavor Diatchki wrote:
>> I use git for a lot of my development...
>> Given the responses though, it sounds like this is a well known
>> problem with darcs with no obvious solution.
>
> Why do you say there is no obvious solution? In fact, Ganesh,
> representing the Darcs tea
I've done a bit more chewing away at the branch and have gotten to
19Sep10.
Edward
___
Glasgow-haskell-users mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Ian, I'd love a little guidance with this patch:
Thu Oct 21 13:08:53 BST 2010 Ian Lynagh
* Use takeUniqFromSupply in emitProcWithConvention
We were using the supply's unique, and then passing the same supply to
initUs_, which sounds like a bug waiting to happen.
{
hunk ./compiler/c
Final status report for tonight, before I crash in bed;
I've managed to make it compile all the way to hoopl.
It seems like hoopl doesn't typecheck anymore? I haven't
been following the typechecker changes too closely so
some guidance would be appreciated.
libraries/hoopl/src/Compiler/Hoopl/Util.h
13 matches
Mail list logo
