History log of /external/libcxx/include/string.h
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
ee226c05af9e0187098f43fb71465a581487af9b 09-Jun-2016 Dan Austin <danielaustin@google.com> Revert "Revert "Update aosp/master libcxx rebase to r263688""

This reverts commit 1d4a1edbc7e4461b59239e1b8297e9dd395a6322.

Change-Id: I2909937fe582f2c5552bc86e7f4d2d5cff0de0aa
/external/libcxx/include/string.h
1d4a1edbc7e4461b59239e1b8297e9dd395a6322 26-May-2016 Dan Albert <danalbert@google.com> Revert "Update aosp/master libcxx rebase to r263688"

The world is burning.

This reverts commit c004fd909c006eec55077c52ee119e1fa338c9e9, reversing
changes made to 1418e4163da4bb0b9e3fe496e51c23a0dce399d9.
/external/libcxx/include/string.h
ebe55fc655e3ac05e5e8f4881809cf5fc2edc5bf 12-Feb-2016 Richard Smith <richard-llvm@metafoo.co.uk> Instead of asking glibc to provide correct C++ signatures for <string.h>
functions, ask it whether it did provide them after the fact. Some versions of
glibc fail to compile if you make this request and don't also claim to be at
least GCC 4.3.


git-svn-id: https://llvm.org/svn/llvm-project/libcxx/trunk@260622 91177308-0d34-0410-b5e6-96231b3b80d8
/external/libcxx/include/string.h
35c6f011ac5fa3c4ce507681808b006d19087971 11-Feb-2016 Richard Smith <richard-llvm@metafoo.co.uk> Work around regression in glibc 2.22: request that glibc provides the correct
prototypes for <string.h> functions that are converted into overload sets in
C++. This matches the existing workaround in <wchar.h>.


git-svn-id: https://llvm.org/svn/llvm-project/libcxx/trunk@260570 91177308-0d34-0410-b5e6-96231b3b80d8
/external/libcxx/include/string.h
b4aa97130b8ba78944943cdd1e952b9b2ed1d423 10-Feb-2016 Richard Smith <richard-llvm@metafoo.co.uk> Fix overload sets of strchr, strpbrk, strrchr, memchr and strstr from
<string.h> and wcschr, wcspbrk, wcsrchr, wmemchr, and wcsstr from <wchar.h> to
provide a const-correct overload set even when the underlying C library does
not.

This change adds a new macro, _LIBCPP_PREFERRED_OVERLOAD, which (if defined)
specifies that a given overload is a better match than an otherwise equally
good function declaration without the overload. This is implemented in modern
versions of Clang via __attribute__((enable_if)), and not elsewhere.

We use this new macro to define overloads in the global namespace for these
functions that displace the overloads provided by the C library, unless we
believe the C library is already providing the correct signatures.


git-svn-id: https://llvm.org/svn/llvm-project/libcxx/trunk@260337 91177308-0d34-0410-b5e6-96231b3b80d8
/external/libcxx/include/string.h
9d6ca4962b429a6b8a401b84a6e61eb88f0d12da 30-Oct-2015 Richard Smith <richard-llvm@metafoo.co.uk> Revert r249929 ("Split <string.h> out of <cstring>").

This change caused problems when building code like povray that:
a) uses 'using namespace std;'
b) is built on an environment where the C library provides the "wrong"
(non-const-correct) interface for the str* functions
c) makes an unqualified call to one of those str* functions

A patch is out for review to add a facility to fix this (and to give the
correct signatures for these functions whenever possible, even when the C
library does not do so). This revert is expected to be temporary.


git-svn-id: https://llvm.org/svn/llvm-project/libcxx/trunk@251665 91177308-0d34-0410-b5e6-96231b3b80d8
/external/libcxx/include/string.h
9f4f08db91e0a7bdeb20a52b80db566d328882ec 10-Oct-2015 Richard Smith <richard-llvm@metafoo.co.uk> Split <string.h> out of <cstring>.

Also fix the overload set for the five functions whose signatures change in the
case where we can fix it. This is already covered by existing tests for the
affected systems.


git-svn-id: https://llvm.org/svn/llvm-project/libcxx/trunk@249929 91177308-0d34-0410-b5e6-96231b3b80d8
/external/libcxx/include/string.h