David, As this is only about the LLVM backend, I would propose to just use the clang assembler and not worry about as/gcc.
People who are stuck with OS X 10.5 might not be able to use the LLVM backend with clang, but they can still use the NCG, and they will be a small minority. OS X users upgrade OSes very quickly. Apple is quickly moving away from gcc, so on OS X, I would strongly suggest we do them same. Manuel David Terei: > Hi Manuel and all, > > GHC 7.4 with LLVM 3.0 on OSX doesn't work correctly because LLVM as of > 3.0 generates assembly code that is incompatible with the system > linker. (used through as or gcc). After talking to the LLVM guys it > turns out this is a deliberate choice. The OS X system assembler isn't > moving forward and the LLVM people don't want to worry about working > around its bugs / limitations, so they only support their own > assembler. I've just tested on OS X with using clang as the assembler > and everything is great! > > So I want to change GHC to use clang as the assembler. My question to > people more in the know with OS X is, whats the story in regards to > when and where clang is installed on OSX? Can we expect all OSX users > to have it installed by default? Or is it only from say 10.7 > onwards... ect? > > Cheers, > David > > _______________________________________________ > Cvs-ghc mailing list > Cvs-ghc@haskell.org > http://www.haskell.org/mailman/listinfo/cvs-ghc _______________________________________________ Cvs-ghc mailing list Cvs-ghc@haskell.org http://www.haskell.org/mailman/listinfo/cvs-ghc
