Change GHC to use clang on OSX as the assembler driver
nominolo at googlemail.com
Thu Nov 3 16:39:30 CET 2011
I'm pretty sure Clang doesn't come with 10.5. I don't remember having
to do anything special with 10.6, but I don't know whether 10.6's
version is compatible with the latest version. How can I find out?
As for my personal stance on upgrading: My 10.5 laptop is a 1st-gen
MacBook which are 32 bit only, so it doesn't make much sense to
upgrade to 10.6. My work Mac does run 10.6 but I've only heard of
people having problems with 10.7, so it'll take a long time until I
will feel confident to take that step. I think Bryan O'Sullivan
recently reported having issues after upgrading to 10.7 as well. Thus
I assume many will wait to upgrade, as well.
On 3 November 2011 07:01, David Terei <davidterei at gmail.com> wrote:
> 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?
> Cvs-ghc mailing list
> Cvs-ghc at haskell.org
Push the envelope. Watch it bend.
More information about the Cvs-ghc