summaryrefslogtreecommitdiffstats
path: root/libcxx/test
Commit message (Collapse)AuthorAgeFilesLines
* Fix string conversions functions to throw out_of_range properly. Fixes ↵Howard Hinnant2013-01-142-4/+14
| | | | | | http://llvm.org/bugs/show_bug.cgi?id=14919. llvm-svn: 172447
* Michael van der Westhuizen: Improve support for testing on Linux. Fixes ↵Howard Hinnant2013-01-142-6/+30
| | | | | | http://llvm.org/bugs/show_bug.cgi?id=14892. llvm-svn: 172436
* Michael van der Westhuizen: Patches for Linux. Fixes ↵Howard Hinnant2013-01-141-1/+1
| | | | | | http://llvm.org/bugs/show_bug.cgi?id=14648. llvm-svn: 172435
* Fix exception safety bug in vector::push_backHoward Hinnant2013-01-116-0/+438
| | | | llvm-svn: 172250
* Made test output iterators have value_type of 'void'; matches ones in libraryMarshall Clow2013-01-092-1/+14
| | | | llvm-svn: 171980
* Move common header files into a 'support' directory; make 'testit' include ↵Marshall Clow2013-01-05364-388/+389
| | | | | | -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
* atomic_bool was missing (just a typedef to atomic<bool>).Howard Hinnant2013-01-041-0/+57
| | | | llvm-svn: 171498
* ...and then there was one. Only one copy of 'iterators.h' in the test tree ↵Marshall Clow2013-01-04113-762/+152
| | | | | | for libc++ llvm-svn: 171479
* Removed another copy of 'iterators.h' files in libcxx/testMarshall Clow2013-01-0359-336/+58
| | | | llvm-svn: 171456
* Removed several more different 'iterators.h' files in libcxx/testMarshall Clow2013-01-03134-883/+131
| | | | llvm-svn: 171452
* Removed 7 (of 8) different 'iterators.h' files in test/localizationMarshall Clow2013-01-0366-355/+85
| | | | llvm-svn: 171443
* Klaas de Vries: Fix bug in libc++'s std::string::find_first_not_of.Howard Hinnant2012-12-311-0/+2
| | | | llvm-svn: 171321
* Test case for http://llvm.org/bugs/show_bug.cgi?id=14670.Howard Hinnant2012-12-201-0/+2
| | | | llvm-svn: 170706
* Added static_assert to std::get<N>(std::array) calls to catch "out of ↵Marshall Clow2012-12-181-0/+25
| | | | | | bounds" calls llvm-svn: 170435
* Zhang Xiongpang: Add definitions for const data members. Fixes ↵Howard Hinnant2012-12-1213-0/+308
| | | | | | http://llvm.org/bugs/show_bug.cgi?id=14585. llvm-svn: 170026
* Modify testit to use the local headers and lib. Thanks go to Jeffrey Yasskin.Howard Hinnant2012-12-091-0/+28
| | | | llvm-svn: 169686
* tests/lit: Change test default parameters to assume local build.Daniel Dunbar2012-11-271-17/+29
| | | | | | - Also, support overriding them with lit parameters. llvm-svn: 168749
* Add overflow check to tanh(complex) and reduce to finite answer. Fixes ↵Howard Hinnant2012-09-191-0/+1
| | | | | | http://llvm.org/bugs/show_bug.cgi?id=13874 llvm-svn: 164266
* Loosen up the timing requirements on 4 more tests.Howard Hinnant2012-08-044-4/+4
| | | | llvm-svn: 161289
* Andrew Morrow: There are two tests under test/utilities/memory that heap ↵Howard Hinnant2012-08-022-4/+0
| | | | | | | | | | | | | allocate two integers which remain unused and are subsequently leaked, so the test fail when run under valgrind. Unless I'm overlooking a subtle reason why they are needed I think they can be removed, allowing these tests to pass under valgrind. The attached patch removes the variables. If there is a reason for them to exist, I can change this to just delete them at the end of the test. llvm-svn: 161195
* Andrew Morrow: The attached patch updates the lit.config for libc++ unit ↵Howard Hinnant2012-08-021-0/+2
| | | | | | | | | tests so that the valgrind configuration passed to lit.py is used to run .pass tests. llvm-svn: 161193
* Andrew Morrow: This patch fixesHoward Hinnant2012-08-021-1/+1
| | | | | | | | | test/input.output/iostream.format/output.streams/ostream.formatted/ostream.inserters.arithmetic/pointer.pass.cpp to accept '(nil)' as a valid representation for NULL so that the test passes on Linux. The same thing is already done in some other tests, like in /test/localization/locale.categories/category.numeric/locale.nm.put/facet.num.put.members/put_pointer.pass.cpp. llvm-svn: 161188
* Implement [util.smartptr.shared.atomic]. This is the last unimplementedHoward Hinnant2012-07-3011-0/+409
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | section in libc++. This requires a recompiled dylib. Failure to rebuild the dylib will result in a link-time error if and only if the functions from [util.smartptr.shared.atomic] are used. The implementation is not lock free. After considerable thought, I know of no way to make the implementation lock free. Ideas welcome along that front. But changing the ABI of shared_ptr is not on the table at this point. The mutex used to lock these function is encapsulated by std::__sp_mut. The only thing the client knows about std::__sp_mut is that it has a void* data member, can't be constructed, and has lock and unlock members. Within the binary __sp_mut is currently implemented as a pointer to a std::mutex. That can change in the future without disturbing the ABI (as long as sizeof(__sp_mut) remains constant. I specifically did not make __sp_mut a spin lock as I have a pathological distrust of spin locks. Testing on OS X reveals that the use of std::mutex in this role is not a large performance penalty as long as the contention for the mutex is low (more likely to get the lock than to have to wait). In the future we can still make __sp_mut a spin lock if that is what is desired (without ABI damage). The dylib contains 16 __sp_mut's to be chosen based on the hash of the address of the shared_ptr. The constant 16 is a ball-park reasonable space/time tradeoff. std::hash<T*> was changed to call __murmur2_or_cityhash, instead of the identity function. I had thought we had already done this, but I was mistaken. All of this is under #if __has_feature(cxx_atomic) even though the implementation is not lock free, because the signatures require access to std::memory_order, which is currently available only under __has_feature(cxx_atomic). llvm-svn: 160940
* <algorithm> no longer needs to include <cstdlib>, but can get away with just ↵Howard Hinnant2012-07-262-0/+2
| | | | | | <cstddef>. This was brought to my attention by Salvatore Benedetto in his port to a bare-metal coretex-m3. This exposed two test bugs where an explicit #include <cstdlib> was needed. llvm-svn: 160786
* noexcept and constexpr applied to <mutex>.Howard Hinnant2012-07-211-1/+8
| | | | llvm-svn: 160604
* noexcept and constexpr applied to <ios>.Howard Hinnant2012-07-211-0/+3
| | | | llvm-svn: 160593
* constexpr applied to <complex>.Howard Hinnant2012-07-2010-1/+113
| | | | llvm-svn: 160585
* Relax the tolerances on some timing tests.Howard Hinnant2012-07-202-2/+2
| | | | llvm-svn: 160566
* noexcept applied to <iterator>.Howard Hinnant2012-07-201-1/+1
| | | | llvm-svn: 160565
* constexpr applied to <array>.Howard Hinnant2012-07-201-0/+14
| | | | llvm-svn: 160564
* Relax the complete-type checks that are happening under __invokable<Fp, ↵Howard Hinnant2012-07-161-0/+29
| | | | | | Args...> to only check Fp, and not Args... . This should be sufficient to give the desired high quality diagnostics under both bind and function. And this allows a test reported by Rich E on cfe-dev to pass. Tracked by <rdar://problem/11880602>. llvm-svn: 160285
* Applied constexpr to <chrono>.Howard Hinnant2012-07-1325-6/+357
| | | | llvm-svn: 160184
* Fixed a bug in wstring_convert concerning zero-length inputs. Thanks to ↵Howard Hinnant2012-07-122-0/+4
| | | | | | Jonathan Coxhead for reporting this bug. llvm-svn: 160136
* Add test for self-referencing emplace test.Howard Hinnant2012-07-091-0/+34
| | | | llvm-svn: 159921
* Apply constexpr to <bitset>.Howard Hinnant2012-07-073-2/+5
| | | | llvm-svn: 159899
* Give tuple a constexpr default constructor.Howard Hinnant2012-07-061-0/+14
| | | | llvm-svn: 159857
* Add noexcept test for offsetof macro per [support.types]/p4.Howard Hinnant2012-07-061-0/+8
| | | | llvm-svn: 159846
* This commit establishes a new bucket_count policy in the unordered ↵Howard Hinnant2012-07-064-4/+4
| | | | | | 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
* Fix a few testsuite bugs involving trailing null (or lack thereof) in strstream.Howard Hinnant2012-06-015-7/+7
| | | | llvm-svn: 157832
* The rules for emplace in map, multimap, unordered_map and unordered_multimap ↵Howard Hinnant2012-05-259-12/+33
| | | | | | changed a while back and I'm just now updating to these new rules. In a nutshell, you've got to know you're emplacing to a pair and use one of pair's constructors. I made one extension: If you want to emplace the key and default construct the mapped_type, you can just emplace(key), as opposed to emplace(piecewise_construct, forward_as_tuple(key), forward_as_tuple()). llvm-svn: 157503
* libc++: Add some missing #includes to atomics tests. libc++ doesn't need theseRichard Smith2012-04-1925-1/+25
| | | | | | | at the moment, but they allow these tests to be used to test clang against libstdc++. Add myself to the credits file, as suggested by Howard. llvm-svn: 155085
* Fix the remaining atomic tests, all of which were wrong for the case where aDavid Chisnall2012-04-057-16/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | compare-and-exchange failed (it should update the expected value to the current value, and the tests were checking that it didn't...). Results of the atomics part of the test suite on FreeBSD with clang trunk and the atomic.c from compiler-rt (currently kludged into the test, not installed properly): **************************************************** Results for /root/libc++/test/atomics: using clang version 3.1 (trunk 153415) Target: x86_64-unknown-freebsd10.0 Thread model: posix with -std=c++0x -stdlib=libc++ -pthread /tmp/atomic.o ---------------------------------------------------- sections without tests : 0 sections with failures : 0 sections without failures: 14 + ---- total number of sections : 14 ---------------------------------------------------- number of tests failed : 0 number of tests passed : 52 + ---- total number of tests : 52 **************************************************** Yay! llvm-svn: 154095
* Fix test cases that were trying to make atomic things that are not trivially ↵David Chisnall2012-04-0511-44/+0
| | | | | | | | copyable. Now all of the test cases compile. Some of them even run! llvm-svn: 154094
* Update <random> with constexpr support. Patch contributed by Jonathan Sauer.Howard Hinnant2012-04-024-12/+20
| | | | llvm-svn: 153896
* Fix test for default constructor of discrete_distribution. This partially ↵Howard Hinnant2012-04-021-6/+3
| | | | | | addresses http://llvm.org/bugs/show_bug.cgi?id=12436. llvm-svn: 153873
* I believe tuple is still under development in the standard. Daniel Krugler ↵Howard Hinnant2012-04-012-4/+25
| | | | | | is/will be making convincing arguments that a modified form of LWG 2051 (currently NAD Future) is easily acheivable and desirable. He has demonstrated that a tuple<T...> where all of the T are implicitly convertible from U... should have a tuple constructor that is also implicit, instead of explicit. This would support the use cases in LWG 2051 while not undermining T... with explicit conversions from U.... This check-in is an experimental implementation of Daniel's work. I believe this work to be mature enough to warrant inclusion into libc++. If anyone sees real-world problems that this check in causes, please let me know and I will revert it, and provide the feedback to the LWG. llvm-svn: 153855
* Allow libc++ to be built with CMake from within the LLVM tree. The libc++ ↵Howard Hinnant2012-03-191-1/+1
| | | | | | part is just some renaming as the variable was already in use, conflicting with something else in the LLVM tree. Contributed by Ruben Van Boxem. llvm-svn: 153036
* Don't refer to a function that doesn't exist in the quick_exit test.David Chisnall2012-03-141-1/+1
| | | | llvm-svn: 152716
* Fix moneypunct_byname algorithm to more accurately represent C locales in C++.Jeffrey Yasskin2012-03-106-150/+147
| | | | llvm-svn: 152501
* Make the failure reporting in testit a bit more useful.David Chisnall2012-02-291-2/+4
| | | | llvm-svn: 151719
OpenPOWER on IntegriCloud