RPCS3/llvm
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm.git synced 2024-12-27 14:45:50 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
b0bdcb5f8a
llvm/lib/Support/Unix
History
Rafael Espindola b0bdcb5f8a make getLastModificationTime const. Move it with the other getters. 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@184478 91177308-0d34-0410-b5e6-96231b3b80d8
2013-06-20 21:51:49 +00:00
..
Host.inc
Memory.inc Remove declaration of __clear_cache for __APPLE__. <rdar://problem/13924072> 2013-05-19 20:33:51 +00:00
Mutex.inc
Path.inc Remove Path::getDirectoryContents. 2013-06-19 15:32:37 +00:00
PathV2.inc make getLastModificationTime const. Move it with the other getters. 2013-06-20 21:51:49 +00:00
Process.inc Remove MSan hack that is no longer needed. 2013-06-20 14:19:10 +00:00
Program.inc Replace use of PathV1.h in Program.cpp. 2013-06-14 19:38:45 +00:00
README.txt
RWMutex.inc
Signals.inc Don't use PathV1.h in Signals.h. 2013-06-13 21:16:58 +00:00
system_error.inc
ThreadLocal.inc
TimeValue.inc Fix initialization-order bug in llvm::Support::TimeValue. TimeValue::now() is explicitly called during module initialization of lib/Support/Process.cpp. It reads the field of global object PosixZeroTime, which is not guaranteed to be initialized at this point. Found by AddressSanitizer with -fsanitize=init-order option. 2013-02-19 11:35:39 +00:00
Unix.h Sort includes for all of the .h files under the 'lib' tree. These were 2012-12-04 07:12:27 +00:00
Watchdog.inc Add a new watchdog timer interface. The interface does not permit handling timeouts, so 2013-03-26 01:27:52 +00:00

README.txt 

llvm/lib/Support/Unix README
===========================

This directory provides implementations of the lib/System classes that
are common to two or more variants of UNIX. For example, the directory
structure underneath this directory could look like this:

Unix           - only code that is truly generic to all UNIX platforms
  Posix        - code that is specific to Posix variants of UNIX
  SUS          - code that is specific to the Single Unix Specification
  SysV         - code that is specific to System V variants of UNIX

As a rule, only those directories actually needing to be created should be
created. Also, further subdirectories could be created to reflect versions of
the various standards. For example, under SUS there could be v1, v2, and v3
subdirectories to reflect the three major versions of SUS.