Hi all,
I forgot I once raised this on the GHC bug tracker:
http://hackage.haskell.org/trac/ghc/ticket/7025
Here's what Simon M had to say back then:
The right thing is to put -msse in the cc-options field of your
.cabal file, if that's what you want.
I'm distinctly uneasy about having -msse
On Thu, Jan 17, 2013 at 12:01 PM, Johan Tibell johan.tib...@gmail.com wrote:
I forgot I once raised this on the GHC bug tracker:
http://hackage.haskell.org/trac/ghc/ticket/7025
Here's what Simon M had to say back then:
The right thing is to put -msse in the cc-options field of your
.cabal
On 17/01/13 20:06, Johan Tibell wrote:
On Thu, Jan 17, 2013 at 12:01 PM, Johan Tibell johan.tib...@gmail.com wrote:
I forgot I once raised this on the GHC bug tracker:
http://hackage.haskell.org/trac/ghc/ticket/7025
Here's what Simon M had to say back then:
The right thing is to put -msse in
On Thu, Jan 17, 2013 at 12:29 PM, Simon Marlow marlo...@gmail.com wrote:
If the intended meaning of -msse is
Use SSE instructions in Haskell compilations
then of course we should pass -mattr=+sse to LLVM, because it is the backend
for Haskell compilations. But we should not pass it to
Hi all,
You can turn on e.g. SSE 4.1 by passing -msse4.2 to ghc. This doesn't
currently imply that we compile any C code with -msse4.2 turned on, so
if someone really want to use SSE4.2, they have to do:
ghc -msse4,2 -optc-msse4.2
Do we want to change this so it's enough to pass -msse4.2 to
On 11 January 2013 06:10, Johan Tibell johan.tib...@gmail.com wrote:
Hi all,
You can turn on e.g. SSE 4.1 by passing -msse4.2 to ghc. This doesn't
currently imply that we compile any C code with -msse4.2 turned on, so
if someone really want to use SSE4.2, they have to do:
ghc -msse4,2
