[cfe-dev] what bigger clang MSVC compatible checks?

[Reid Kleckner]

Right now I test the MSVC compatibility by trying to build something big
with /fallback, like:
- Clang + LLVM: this works now, we can selfhost
- Chromium (http://llvm.org/bugs/show_bug.cgi?id=18887)
- Firefox (I've seen bug reports from people trying this, but I've never
tried it)

Notably, the first two of those projects don't need RTTI, exceptions, or
dllexport/dllimport of classes, which are the big gaps in Clang's
compatibility today.

Having some amount of fallback keeps us honest w.r.t. ABI compatibility,
but these days we don't fall back very often.  Soon we'll have to take a
more aggressive approach of mixing and matching object files between MSVC
and Clang before linking and testing the resulting binary.


On Thu, Mar 27, 2014 at 10:57 PM, Dennis Luehring <dl.soluz at gmx.net> wrote:

> according to
>
> http://clang.llvm.org/docs/MSVCCompatibility.html
> http://llvm.org/bugs/show_bug.cgi?id=12477
>
> there are still some/many open issues for getting MSVC compatible
>
> my question is: how is the testing done? are there many test-cases around
> or
> also compile/link-test against librarys like Qt or other big ones?
> _______________________________________________
> 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/20140328/14626aea/attachment.html>