[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using labels-as-values on MacOS X

From: Hans Aberg
Subject: Re: Using labels-as-values on MacOS X
Date: Sat, 26 May 2012 14:58:42 +0200

On 26 May 2012, at 14:44, Ludovic Courtès wrote:

> Hans Aberg <address@hidden> skribis:
>> On 25 May 2012, at 17:31, Ludovic Courtès wrote:
>>> Ken Raeburn <address@hidden> skribis:
>>>> * Don't use addresses of code labels with LLVM, even if the compiler
>>>> supports them.  At least with the version of LLVM GCC on my Mac ("gcc
>>>> version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
>>>> 2336.1.00)"),
>>> Damn, what compiler is this?  It’s not the old GCC 4.2 fork?  Is it
>>> Clang?  GCC with DragonEgg?
>> $ /usr/bin/gcc --version
>> i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 
>> 5658) (LLVM build 2336.9.00)
>> $ ls -l /usr/bin/gcc
>> lrwxr-xr-x  1 root  wheel  12 Mar 23 21:20 /usr/bin/gcc -> llvm-gcc-4.2
> They put so much effort into making a compiler indistinguishable from
> GCC that all we can hope for is that it generates code that performs as
> well as GCC’s.  I wouldn’t want to #ifdef around these shameless hacks.

When compiling packages, I normally use /usr/bin/gcc, which is llvm-gcc then, 
because I think it was what package writer normally would expect. So 
'configure' normally chooses gcc, which then becomes llvm-gcc unless one is 
doing something, like setting CC or installing ones own GCC.

Otherwise, the system compiler is now actually clang:
  $ ls -l /usr/bin/cc
  /usr/bin/cc -> clang
Before it was LLVM-GCC which still has a link from /usr/bin/gcc.

> Thanks for the info!

You are welcome.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]