rsmith added a comment.

Hmm, this won't help when building libc++ as a module, and we don't have a 
wrapper header to hold these undefs since <stdatomic.h> is not part of c++.

So either that combination of includes gives a broken <atomic> or a broken 
<stdatomic.h>, or we do something nonstandard like reimplementing the latter in 
terms of the former in libc++.

Eric, Marshall, what do you think? How / how much should we support this 
non-c++ header?


https://reviews.llvm.org/D26376



_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to