I remember reading somewhere that packages that use parallelism, like `repa`, would benefit from the llvm backend. I've never seen benchmarks though.


On Sun, Apr 27, 2014 at 11:55 PM, Magnus Therning <magnus@therning.org> wrote:
On Sun, Apr 27, 2014 at 11:11:25PM +0200, Nicola Squartini wrote:
> I never used LLVM so I'm looking at the manual right now. It's explained
> here:
>
> http://llvm.org/docs/CommandGuide/llc.html#cmdoption-mcpu
>
> It autodetects the cpu and optimizes for it.
> As I understand, in order to produce generic code you should pass
> -mcpu=i686 or -mcpu=x86_64. They can be passed to the ghc via -optlc, e.g.
> -optlc="-mcpu=x86_64".
> I'm going to look more carefully to see what is the best option to pass.

Thanks for looking into it.

This does makes me wonder though what other differences there are
between the two code generators.  Maybe it's worth considering using
LLVM for all packages?

/M

--
Magnus Therning                      OpenPGP: 0xAB4DFBA4
email: magnus@therning.org   jabber: magnus@therning.org
twitter: magthe               http://therning.org/magnus

What gets measured, gets done.
     -- Tom Peters