llvm dev - Aug 2014 - [LLVMdev] [cfe-dev] [RFC] Raising LLVM minimum required MSVC version to 2013 for trunk

On Aug 23, 2014, at 1:24 PM, Renato Golin <renato.golin at linaro.org>
wrote:
> 
> Also,
> compiling Clang with MSVC and making Clang MSVC compatible are two
> completely different things. A commercial toolchain based on MSVC
> compatibility doesn't necessarily need to be compiled with MSVC
> itself.
But it must. If you want to be able to use LLVM DLLs inside a Windows app, it
has to be built with MSVC because they have their own C++ ABI.  At some point,
Clang will support Microsoft's ABI well enough to consider a bootstrap
instead.

Alex

On 24 August 2014 02:05, Alex Rosenberg <alexr at leftfield.org>
wrote:
> But it must. If you want to be able to use LLVM DLLs inside a Windows app,
it has to be built with MSVC because they have their own C++ ABI.  At some
point, Clang will support Microsoft's ABI well enough to consider a
bootstrap instead.
Ah, there's my answer! I thought we were at that stage already.

cheers,
--renato

On Aug 24, 2014, at 5:08 AM, Renato Golin <renato.golin at linaro.org>
wrote:
> On 24 August 2014 02:05, Alex Rosenberg <alexr at leftfield.org>
wrote:
>> But it must. If you want to be able to use LLVM DLLs inside a Windows
app, it has to be built with MSVC because they have their own C++ ABI.  At some
point, Clang will support Microsoft's ABI well enough to consider a
bootstrap instead.
> 
> Ah, there's my answer! I thought we were at that stage already.
While admirable progress has been made, AFAIK, no attempt has begun to get
debugging working. It is not practical to use LLVM from within a Windows
application today unless it's built with MSVC.

Alex