RPCS3/llvm
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm.git synced 2024-12-11 13:44:28 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
190717d3cf
llvm/lib/System/Unix
History
Chris Lattner 505f9c8839 This function is not documented as throwing an exception and callers don't 
handle it.  Just silently fail.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@28291 91177308-0d34-0410-b5e6-96231b3b80d8
2006-05-14 18:53:09 +00:00
..
SUS Remove vim settings from source code; people should use llvm/utils/vim/vimrc 2005-05-05 22:33:09 +00:00
Alarm.inc Implement a generic polled Alarm function. This merely removes the system 2005-12-22 03:23:46 +00:00
MappedFile.inc Remove vim settings from source code; people should use llvm/utils/vim/vimrc 2005-05-05 22:33:09 +00:00
Memory.inc support near allocations for the JIT 2005-07-29 23:40:16 +00:00
Mutex.inc For PR540: 2005-07-12 15:37:43 +00:00
Path.inc Fix a problem in getDirectoryContents where sub-directory names were 2005-07-28 16:25:57 +00:00
Process.inc This function is not documented as throwing an exception and callers don't 2006-05-14 18:53:09 +00:00
Program.inc For PR351: 2005-12-22 20:00:16 +00:00
README.txt Fix a typo. 2004-08-26 07:43:33 +00:00
Signals.inc Implement sys::SetInterruptFunction on Unix, stub it on win32 so that the 2005-08-02 02:14:22 +00:00
TimeValue.inc comment the hpux bit 2005-05-16 06:59:53 +00:00
Unix.h Remove trailing whitespace 2005-04-21 22:55:34 +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.