summaryrefslogtreecommitdiffstats
path: root/libcxx/test/std/utilities/date.time
Commit message (Collapse)AuthorAgeFilesLines
* Move test/std/utilities/date.time to proper stable name utilities/time/date.timeEric Fiselier2015-08-245-112/+0
| | | | llvm-svn: 245877
* Misc drive-by cleanups. NFCJonathan Roelofs2015-08-241-0/+2
| | | | | | http://reviews.llvm.org/D12294 llvm-svn: 245876
* Make support for thread-unsafe C functions optional.Ed Schouten2015-06-244-0/+72
| | | | | | | | | | | | | | | | | | | | | | | | One of the aspects of CloudABI is that it aims to help you write code that is thread-safe out of the box. This is very important if you want to write libraries that are easy to reuse. For CloudABI we decided to not provide the thread-unsafe functions. So far this is working out pretty well, as thread-unsafety issues are detected really early on. The following patch adds a knob to libc++, _LIBCPP_HAS_NO_THREAD_UNSAFE_C_FUNCTIONS, that can be set to disable thread-unsafe functions that can easily be avoided in practice. The following functions are not thread-safe: - <clocale>: locale handles should be preferred over setlocale(). - <cstdlib>: mbrlen(), mbrtowc() and wcrtomb() should be preferred over their non-restartable counterparts. - <ctime>: asctime(), ctime(), gmtime() and localtime() are not thread-safe. The first two are also deprecated by POSIX. Differential Revision: http://reviews.llvm.org/D8703 Reviewed by: marshall llvm-svn: 240527
* Get tests running with warnings. Fix warnings in headers and testsEric Fiselier2015-02-051-0/+1
| | | | llvm-svn: 228344
* Move test into test/std subdirectory.Eric Fiselier2014-12-201-0/+37
llvm-svn: 224658
OpenPOWER on IntegriCloud