llvm dev - Jul 2010 - [LLVMdev] LLVM-C headers: create native library

> The clang driver generally uses an installed gcc to do the assemble
> and link steps at the moment.
gcc? I thought it uses binutils.

Eugene

On Wed, Jul 7, 2010 at 1:55 PM, Eugene Toder <eltoder at gmail.com>
wrote:
>> The clang driver generally uses an installed gcc to do the assemble
>> and link steps at the moment.
>
> gcc? I thought it uses binutils.
It does.  But clang uses the gcc driver to invoke the binutils tools
anyway.  Presumably it's easier that way.

Reid

On Jul 7, 2010, at 1:55 PM, Eugene Toder wrote:
>> The clang driver generally uses an installed gcc to do the assemble
>> and link steps at the moment.
> 
> gcc? I thought it uses binutils.

The gcc driver that runs whatever is appropriate for the system.

-eric

I see. I assumed it runs binutils directly.

Eugene

On Wed, Jul 7, 2010 at 10:02 PM, Eric Christopher <echristo at apple.com>
wrote:
>
> On Jul 7, 2010, at 1:55 PM, Eugene Toder wrote:
>
>>> The clang driver generally uses an installed gcc to do the assemble
>>> and link steps at the moment.
>>
>> gcc? I thought it uses binutils.
>
>
> The gcc driver that runs whatever is appropriate for the system.
>
> -eric
>

On Jul 7, 2010, at 2:02 PM, Reid Kleckner wrote:
> On Wed, Jul 7, 2010 at 1:55 PM, Eugene Toder <eltoder at gmail.com>
wrote:
>>> The clang driver generally uses an installed gcc to do the assemble
>>> and link steps at the moment.
>> 
>> gcc? I thought it uses binutils.
> 
> It does.  But clang uses the gcc driver to invoke the binutils tools
> anyway.  Presumably it's easier that way.
It only does this when there isn't a clang "ToolChain" description
for the target.  On the mac, clang doesn't go through gcc to run the
assembler.

-Chris