RPCS3/llvm
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm.git synced 2024-12-28 23:43:50 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
f11a5fc12d
llvm/lib/Support/Unix
History
Benjamin Kramer 00e08fcaa0 Canonicalize header guards into a common format. 
Add header guards to files that were missing guards. Remove #endif comments
as they don't seem common in LLVM (we can easily add them back if we decide
they're useful)

Changes made by clang-tidy with minor tweaks.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@215558 91177308-0d34-0410-b5e6-96231b3b80d8
2014-08-13 16:26:38 +00:00
..
Host.inc Support: normalize the default triple on Unix 2014-03-30 03:22:37 +00:00
Memory.inc Revert: r211588 - [mips] Use __clear_cache builtin instead of cacheflush() in Unix Memory::InvalidateInstructionCache() 2014-06-24 13:53:56 +00:00
Mutex.inc Now to chant the magical incantation that will exorcise the System library 2010-11-29 19:44:50 +00:00
Path.inc Remove dead code. Fixes pr20544. 2014-08-08 21:35:52 +00:00
Process.inc Remove 'using std::errro_code' from lib. 2014-06-13 02:24:39 +00:00
Program.inc lldb can interrupt waitpid, so EINTR shouldn't be an error. This fixes the case 2014-06-27 18:02:54 +00:00
README.txt
RWMutex.inc Fix RWMutex to be thread-safe when pthread_rwlock is not available 2014-03-01 04:30:32 +00:00
Signals.inc [C++] Use 'nullptr'. 2014-04-28 04:05:08 +00:00
ThreadLocal.inc Make sys::ThreadLocal<> zero-initialized on non-thread builds (PR18205) 2013-12-19 20:32:44 +00:00
TimeValue.inc [C++] Use 'nullptr'. 2014-04-28 04:05:08 +00:00
Unix.h Canonicalize header guards into a common format. 2014-08-13 16:26:38 +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.