Howard Hinnant
|
307f814372
|
Implement full support for non-pointer types in custom allocators. This is for the unordered containers only. This work still needs to be done on the sequence containers.
llvm-svn: 184635
|
2013-06-22 15:21:29 +00:00 |
|
Marshall Clow
|
322270842c
|
Move common header files into a 'support' directory; make 'testit' include -I to that directory; rename 'iterators.h' to 'iterator_test.h'; remove hard-coded paths to include files from more than 350 source files
llvm-svn: 171594
|
2013-01-05 03:21:01 +00:00 |
|
Marshall Clow
|
cf1589f749
|
Removed several more different 'iterators.h' files in libcxx/test
llvm-svn: 171452
|
2013-01-03 02:29:29 +00:00 |
|
Howard Hinnant
|
4cb38a82a2
|
This commit establishes a new bucket_count policy in the unordered containers: The policy now allows a power-of-2 number of buckets to be requested (and that request honored) by the client. And if the number of buckets is set to a power of 2, then the constraint of the hash to the number of buckets uses & instead of %. If the client does not specify a number of buckets, then the policy remains unchanged: a prime number of buckets is selected. The growth policy is that the number of buckets is roughly doubled when needed. While growing, either the prime, or the power-of-2 strategy will be preserved. There is a small run time cost for putting in this switch. For very cheap hash functions, e.g. identity for int, the cost can be as high as 18%. However with more typical use cases, e.g. strings, the cost is in the noise level. I've measured cases with very cheap hash functions (int) that using a power-of-2 number of buckets can make look up about twice as fast. However I've also noted that a power-of-2 number of buckets is more susceptible to accidental catastrophic collisions. Though I've also noted that accidental catastrophic collisions are also possible when using a prime number of buckets (but seems far less likely). In short, this patch adds an extra tuning knob for those clients trying to get the last bit of performance squeezed out of their hash containers. Casual users of the hash containers will not notice the introduction of this tuning knob. Those clients who swear by power-of-2 hash containers can now opt-in to that strategy. Clients who prefer a prime number of buckets can continue as they have.
llvm-svn: 159836
|
2012-07-06 17:31:14 +00:00 |
|
Howard Hinnant
|
1196716270
|
unord test fixes by Edward Meewis
llvm-svn: 145707
|
2011-12-02 21:23:14 +00:00 |
|
Howard Hinnant
|
54976f2619
|
Fixed PR10574: http://llvm.org/bugs/show_bug.cgi?id=10574
llvm-svn: 137522
|
2011-08-12 21:56:02 +00:00 |
|
Howard Hinnant
|
557da866a3
|
noexcept for <unordered_set>.
llvm-svn: 132647
|
2011-06-04 20:18:37 +00:00 |
|
Howard Hinnant
|
2774545736
|
Bug 9096 - list::iterator not default constructible
llvm-svn: 124508
|
2011-01-28 23:46:28 +00:00 |
|
Howard Hinnant
|
412dbebe1b
|
license change
llvm-svn: 119395
|
2010-11-16 22:09:02 +00:00 |
|
Howard Hinnant
|
7609c9b665
|
Changed __config to react to all of clang's currently documented has_feature flags, and renamed _LIBCPP_MOVE to _LIBCPP_HAS_NO_RVALUE_REFERENCES to be more consistent with the rest of the libc++'s flags, and with clang's nomenclature.
llvm-svn: 113086
|
2010-09-04 23:28:19 +00:00 |
|
Howard Hinnant
|
8f2f7e7c79
|
Fixing whitespace problems
llvm-svn: 111755
|
2010-08-22 00:15:28 +00:00 |
|
Howard Hinnant
|
5b08a8a432
|
Wiped out some non-ascii characters that snuck into the copyright.
llvm-svn: 103516
|
2010-05-11 21:36:01 +00:00 |
|
Howard Hinnant
|
3e519524c1
|
libcxx initial import
llvm-svn: 103490
|
2010-05-11 19:42:16 +00:00 |