RPCS3/llvm
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm.git synced 2024-12-26 22:26:16 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
96fc0d298c
llvm/lib/Support/Unix
History
NAKAMURA Takumi 5adece02b6 Unix/Signals.inc: Let findModulesAndOffsets() built conditionally regarding to (defined(HAVE_BACKTRACE) && defined(ENABLE_BACKTRACES)). [-Wunused-function] 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@219596 91177308-0d34-0410-b5e6-96231b3b80d8
2014-10-13 04:32:43 +00:00
..
Host.inc Unix/Host.inc: Remove <cstdlib>. It has been unused for a long time. 2014-09-24 04:45:02 +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
Path.inc Misc cleanups to the FileSytem api. 2014-09-11 20:30:02 +00:00
Process.inc [Modules] Add some missing includes to make files compile stand-alone. 2014-10-12 22:49:26 +00:00
Program.inc Add writeFileWithSystemEncoding to LibLLVMSuppor. 2014-09-03 20:02:00 +00:00
README.txt
RWMutex.inc
Signals.inc Unix/Signals.inc: Let findModulesAndOffsets() built conditionally regarding to (defined(HAVE_BACKTRACE) && defined(ENABLE_BACKTRACES)). [-Wunused-function] 2014-10-13 04:32:43 +00:00
ThreadLocal.inc
TimeValue.inc Cleaning up static initializers in TimeValue. 2014-08-29 01:05:12 +00:00
Unix.h Canonicalize header guards into a common format. 2014-08-13 16:26:38 +00:00
Watchdog.inc

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.