[lldb-dev] RFC: LLVM should require a working C++11 <thread>, <mutex>, and <atomic>

Chandler Carruth chandlerc at gmail.com
Tue Sep 23 18:02:13 PDT 2014

AKA: MinGW + win32threads is holding LLVM (and all of its subprojects)
back. We need to stop supporting this host platform.

I'm aware of essentially 2 reasonably important use cases for supporting
MinGW + win32threads:

1) Sane host toolchain on Windows that doesn't require downloading MSVC.
(I'm dubious about the value of this one...)

2) Cross-compiling a Windows clang.exe (and other tools) from a Linux (or
other host) box.

Are there others? (And thanks to Reid for explaining these to me!)

I'm somewhat dubious about #1, but if we address #2 it will address any
concerns with #1 anyways.

I would like to propose that we finish implementing libc++ sufficiently to
host Clang on Windows using native Windows APIs to implement things. Then
we document very clearly what is required to download the basic Windows SDK
and cross compile Clang (and any other tools) for Windows using just libc++
and the SDK. No need for MSVC bits, etc. Would this be acceptable?

If not, would it be acceptable to use libc++ on top of mingw (so just
avoiding libstdc++)? I *really* don't want to spend lots of time going
there because it seems like a low-value platform, but we can.

Anyways, I want to tease out anything else required here because if this is
all we need, I think we can make it a reality and get to a much saner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20140923/abfd3eca/attachment.html>

More information about the lldb-dev mailing list