[META][Win64] Selfhosting clang/llvm on/for Windows x64

[llvmbot]

Bugzilla Link	9100
Resolution	FIXED
Resolved on	Jan 26, 2015 00:29
Version	trunk
OS	Windows XP
Depends On	llvm/llvm-bugzilla-archive#9776 #8762 #9149 #9150 #9159 #9291 #9294 #9382 #9444 llvm/llvm-bugzilla-archive#9483 llvm/llvm-bugzilla-archive#10978
Blocks	llvm/llvm-bugzilla-archive#13707
Reporter	LLVM Bugzilla Contributor
CC	@nico,@rubenvb

Extended Description

Known issues(clang);

• LLP64 stuff
• Noncommittal "MinGW32" and "MinGW64".
• toolchain
• include and library path
• when will we get rid of G++'s libstdc++?
• compatibility to mingw64-gcc(predefined macros, ABI, ...)

Known issues(llvm);

• X86-64 CodeGen
  • stack frame
  • tailcall
  • varargs
• JIT
  • stub
  • symbol resolution in JIT
• Debugging (eg. stack frame dump) stuff

[rubenvb]

clang test target output for VS2010
The output for the "clang-test" CMake generated project file run through VS2010. 19 failures, no detailed summary of results displayed.

[rubenvb]

clang test target output for VS2010
Now with complete output. 80 failed tests and 1 unexpected pass.

[rubenvb]

llvm check target output for VS2010
Tests run from Visual Studio 2010. 64 failures.

[nico]

Is this done?

[nico]

I think several folks are using clang to build clang on windows these days. let's call this done.

[llvmbot]

mentioned in issue llvm/llvm-bugzilla-archive#9483

[rubenvb]

mentioned in issue llvm/llvm-bugzilla-archive#9776