On Mon, Oct 31, 2011 at 01:17:02PM -0600, Paul Monday wrote:
>
> Addition of these vectorization functions is going to require some new
> MachOps, once I add a new MachOp, all of the code generators want to know
> about the new MachOp as well
But what's the problem with just not implementing th
The compile time is not the issue.
I'm working on adding SIMD instructions and experimenting with the LLVM side of
things (adding new primtypes / primops). I really just want to add
instructions to the LLVM generation for now and leave native SIMD/SSE
instructions to someone else.
Addition of
On Mon, Oct 31, 2011 at 12:52:59PM -0600, Paul Monday wrote:
> Yeah, I was tracking down the unregistered build semantics ….
>
> Unfortunately, this simply says to the compiler:
> "Don't build USING asm because I'm building on an architecture I don't know",
> it doesn't say "don't build asm (nati
Yeah, I was tracking down the unregistered build semantics ….
Unfortunately, this simply says to the compiler:
"Don't build USING asm because I'm building on an architecture I don't know",
it doesn't say "don't build asm (native code generation)".
Perhaps if I unentangle it from compiler/ghc.cab
Check out this page:
http://hackage.haskell.org/trac/ghc/wiki/Building/Unregisterised
You don't want to do a full unregisterised build if you can avoid it
(although its a viable option) but it gives you a starting point, I
don't know how just putting:
GhcWithNativeCodeGen=NO
in your mk/build.mk
Hmmm, it's more complex then that. Maybe I need to step back and look
differently at this.
I'm adding a series of primops/primtypes that I only care about, for now, being
in the LLVM code generation branch. Someone else will worry about the other
code generation paths.
Is the native code gen
Not that I'm aware of but there are ways that are just as good.
If your working on LLVM you can just do stage1 builds and ghc will
only rebuild the changed files. (cd compiler/; make 1)
If you need stage2 builds for some reason then just fix your stage1 to
stop it being rebuilt and then stage2 sh
Is there a simple way to temporarily turn off the -fasm (compiler/nativeGen)
portion of the build? I'm adding code that is targeted at LLVM and I would
love to take the nativeGen portion of the build out of the loop for a while.
Paul Monday
Parallel Scientific, LLC.
paul.mon...@parsci.com
_
