avoids bugs where, when the allocator's size_type was smaller than int,
the multiplication or division would cause integral promotions and, with
two different integer types as arguments, deduction of the template
arguments would fail.

llvm-svn: 136540

are two motivations for this.

First, this allows users who are specializing __gnu_ext::hash to
continue doing so without changing their code.

Second, SGI specifies hash overloads for char* and const char* that
perform a hash of the string, not of the pointer.

In order to support this, the hashing code for string is factored out.

llvm-svn: 136539

the type name 'data_type', which is specified by the SGI spec as being
the correct type name for the mapped type. The second is an overload of
insert found in standard containers, taking an iterator as a 'hint'
(which we ignore in the standard containers as well). libstdc++'s
implementation includes these overloads, and they are needed to make
insert_iterator work (which I suspect is the real motivation for
including them in the standard containers).

The motivation for including these overloads of insert and leaving the
mapped_type typedef is to make it easier for clients to migrate to the
standard containers.

llvm-svn: 136538

llvm-svn: 136526

llvm-svn: 136291

llvm-svn: 136247

llvm-svn: 136232

llvm-svn: 135897

Optimization of string::operator< by M.E. O'Neill.  Discussion in http://llvm.org/bugs/show_bug.cgi?id=10461

llvm-svn: 135893

llvm-svn: 135873

llvm-svn: 135854

llvm-svn: 135774

llvm-svn: 135460

between C++03 and C++0x and its effect on exceptions, and another two to
not test move construction when rvalue references are not available.

llvm-svn: 135445

hard-coded names.

llvm-svn: 135444

for the tests that open new data files.

llvm-svn: 135422

std::underlying_type.

llvm-svn: 135410

itself non-throwing.  Since nested_exception's destructor is
non-throwing, if B's destructor is not, this causes an error in C++03
mode due to the overriding function having a more lax specification.
This did not occur in C++0x mode as A's destructor was implicitly
non-throwing.

llvm-svn: 135400

llvm-svn: 135393

llvm-svn: 135272

llvm-svn: 135271

proper va_list time on non-darwin platforms.

llvm-svn: 135247

issues with it.

llvm-svn: 135246

llvm-svn: 135125

llvm-svn: 135045

Reverted to 134947.  Once I got into it, I discovered there were too many problems to fix in 135035.

llvm-svn: 135044

all platforms. Unfortunately a lot of this remains conditionally
compiled so as not to break Apple's ABI.

The new _LIBCPP_LOCALE__L_EXTENSIONS macro can be defined on other
platforms that support _l suffixes for all functions in order to use
them.

llvm-svn: 135035

llvm-svn: 134947

llvm-svn: 134843

llvm-svn: 134815

glibc, for instance, it's a const char *.

llvm-svn: 134787

llvm-svn: 134783

traits.

To the best of my knowledge, this will not break the ABI for Apple.
However, it does introduce three publicly visible (although with
reserved name) functions that will fail to link against the just-shipped
Apple version of libc++. Since they are not used in any inline
functions, no actual breakage should occur.

If Howard doesn't want to put undefined functions (even internal ones)
into a header, they could be surrounded by additional conditional
compilation.

llvm-svn: 134781

llvm-svn: 134663

llvm-svn: 134650

llvm-svn: 134639

not test for this.

llvm-svn: 134531

llvm-svn: 134405

llvm-svn: 134375

llvm-svn: 134327