<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 24, 2014 at 8:48 AM, Óscar Fuentes <span dir="ltr"><<a href="mailto:ofv@wanadoo.es" target="_blank">ofv@wanadoo.es</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">David Chisnall <<a href="mailto:David.Chisnall@cl.cam.ac.uk">David.Chisnall@cl.cam.ac.uk</a>> writes:<br>
<br>
> <atomic> is trivial, as most of the support is provided by the<br>
> compiler. As of Vista, Windows comes with some quite sane primitives<br>
> for implementing <mutex> and <thread>, so it would only be 1-2 days of<br>
> work for someone to write the implementation for libc++.<br>
<br>
</span>Forcing Clang to depend on libc++ makes things quite complicated for the<br>
end user. For the Windows case, building Clang without cross-compiling<br>
could be impossible, if it requires that libc++ must be compiled by<br>
Clang.</blockquote></div><br></div><div class="gmail_extra">The only way Clang would depend on libc++ is if you weren't able or willing to use one of the other host toolchains to cross to windows. Both mingw-w64 and the threads-posix stuff which supports C++11 <thread> would work fine as well.</div></div>