[cfe-dev] GSoC Proposal: Improve Windows Support

[endlessroad1991 at gmail.com]

Sorry, my bad. The name mangling suddenly works now. Didn't figure out what
went wrong.

About your local patches, can you publish them somewhere?

The virtual inheritance part, I've traced dynamic_cast, and found it quite
complicated(single inheritance, multiple inheritance, virtual inheritance).
As it's needed for a basic header <iostream>, I think I can start working
on it.
What do you think?


On Thu, Apr 25, 2013 at 3:21 PM, Timur Iskhodzhanov <timurrrr at google.com>wrote:

> 2013/4/25 endlessroad1991 at gmail.com <endlessroad1991 at gmail.com>:
> > What's the current status of clang on Windows?
> We're working on it :)
> With my local patches I can build reasonably complex source code.
> We're in progress upstreaming them but it'll take some time to polish
> them before review/commit process.
>
> > I tried llvm & clang r180250 with MSVC 2012, with "clang++ -Xclang
> -cxx-abi
> > -Xclang microsoft -c 1.cpp"
> > 1. Can't parse MSVC headers. <iostream>, in this case
> iostream is a tough guy - I think clang can't even compile Linux
> headers in the Microsoft ABI mode.
> One has to support virtual inheritance to build iostream<> as both
> basic_istream<> and basic_ostream<> virtually inherit from
> basic_ios<>.
> And we're not working with virtual inheritance correctly in this ABI yet.
>
> > 2. Even if I specified -cxxabi microsoft, "dumpbin /disasm 1.o" gives
> wrong
> > mangled name: _Z1fi for "void f(int)",instead of cl compiled
> > object(?f@@YAXH at Z)
> That looks wrong, symbols are usually mangled correctly to me.
> Can you run with -v and make sure there are no "unknown command line
> argument" warnings?
>



-- 
Best Regards, Tong Shen (沈彤)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20130425/1ef1168b/attachment.html>