FYI, as I commented on the original discussion, I'd personally like to see this
have some versioning scheme before it goes in rather than a binary unstable.
Or some plan for getting there.
Otherwise this looks good as a first step.
http://reviews.llvm.org/D6712
EMAIL PREFERENCES
Added support for lit and CMAKE - thanks to ErikWF for these bits
http://reviews.llvm.org/D6712
Files:
CMakeLists.txt
include/__config
include/string
test/CMakeLists.txt
test/lit.cfg
test/lit.site.cfg.in
EMAIL PREFERENCES
http://reviews.llvm.org/settings/panel/emailpreferences/
Hi chandlerc, EricWF, joerg,
First step towards letting vendors manage ABI changes in libc++.
Introduce the _LIBCPP_ABI_UNSTABLE macro, which turns on all the ABI changes.
Introduce the _LIBCPP_ABI_ALTERNATE_STRING_LAYOUT macro, which controls the
layout of std::string objects. This is a
Will probably want to expose `_LIBCPP_ABI_UNSTABLE` as a cmake option.
http://reviews.llvm.org/D6712
EMAIL PREFERENCES
http://reviews.llvm.org/settings/panel/emailpreferences/
___
cfe-commits mailing list
cfe-commits@cs.uiuc.edu
