[cfe-dev] clang dependence on gcc for assembler even with -filetype=obj

[Daniel Dunbar]

Just the Win32 host info would be a good start.

There should be no need for a Win32Clang or Win32GCC classes. On Win32 we want to just get to the point where the integrated assembler works.

 - Daniel


On Jun 9, 2010, at 10:37, Aaron Gray <aaronngray.lists at gmail.com> wrote:

> On 9 June 2010 17:41, Chris Lattner <clattner at apple.com> wrote:
> 
> On Jun 9, 2010, at 9:39 AM, Aaron Gray wrote:
> 
>> On 9 June 2010 17:29, Chris Lattner <clattner at apple.com> wrote:
>> 
>> On Jun 9, 2010, at 9:20 AM, Aaron Gray wrote:
>> 
>> > Hi,
>> >
>> > I just compiled llvm+clang with MSVC++ and tried using the -filetype=obj but clang seems to be dependent on GCC.
>> 
>> Clang defaults to using GCC as a portability layer for targets that don't have a ToolChain set up in the driver.  Define a ToolChain for your platform and this goes away.
>> 
>> Hi Chris,
>> 
>> Congratulations on your ACM SIGPLAN award.
>> 
>> Sorry to be dumb but how or where do I define a ToolChain ?
> 
> Take a look at clang/docs/DriverInternals.html
> 
> 
> Okay I have to study the code a bit, but basically I have defined a Win32HostInfo class, associated creator, and Driver::GetHostInfo() creator entry.
> 
> next a clang::driver::toolchains::Win32 class ? Should there be ("pure") Win32Clang for native Windows and Win32GCC classes for Cygwin and MinGW to use ?
> 
> Aaron
> 
> 
> 
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20100610/8018ee70/attachment.html>