RPCS3/llvm-mirror
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-12-29 06:53:53 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
5c77da0572
llvm-mirror/lib/System/Unix
History
Duncan Sands 5c77da0572 Using a signal handler that does nothing should be 
equivalent to SIG_IGN.

llvm-svn: 81144
2009-09-07 05:58:25 +00:00
..
Alarm.inc Fix a bunch of namespace pollution. 2009-08-07 01:32:21 +00:00
Host.inc Improve llvm::getHostTriple for some cases where the LLVM_HOSTTRIPLE is not 2009-09-03 01:10:13 +00:00
Memory.inc Re-committing r76828 with the JIT memory manager changes now that the build 2009-07-23 21:46:56 +00:00
Mutex.inc Insert a SmartMutex templated class into the class hierarchy, which takes a template parameter specifying whether this mutex 2009-06-18 17:53:17 +00:00
Path.inc remove the last uses of Config/alloca.h 2009-08-23 22:57:38 +00:00
Process.inc Tweak code into an equivalent form for which icc 2009-09-06 10:53:22 +00:00
Program.inc Using a signal handler that does nothing should be 2009-09-07 05:58:25 +00:00
README.txt
RWMutex.inc Give RWMutex the SmartRWMutex treatment too. 2009-06-18 18:26:15 +00:00
Signals.inc Add locking around signal handler registration. 2009-08-17 17:07:22 +00:00
ThreadLocal.inc Fix compilation without pthreads. 2009-06-26 08:48:03 +00:00
TimeValue.inc Prune #includes from llvm/Linker.h and llvm/System/Path.h, 2009-08-23 22:45:37 +00:00
Unix.h Add a portable strerror*() wrapper, llvm::sys::StrError(). This includes the 2009-07-01 18:11:20 +00:00

README.txt 

llvm/lib/System/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.