RPCS3/llvm
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm.git synced 2024-12-22 12:08:33 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
0c33231eff
llvm/lib/System/Unix
History
Chris Lattner 0c33231eff Modify Path::eraseFromDisk to not throw an exception. 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@29400 91177308-0d34-0410-b5e6-96231b3b80d8
2006-07-28 22:29:50 +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 simple optimization: don't bother calling "exists" (which calls the syscall 2006-07-18 07:07:51 +00:00
Memory.inc Change AllocateRWX/DeallocateRWX to not throw an exception. 2006-07-07 17:32:37 +00:00
Mutex.inc For PR540: 2005-07-12 15:37:43 +00:00
Path.inc Modify Path::eraseFromDisk to not throw an exception. 2006-07-28 22:29:50 +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 Turn an if into an else if. 2006-07-12 22:37:18 +00:00
README.txt Fix a typo. 2004-08-26 07:43:33 +00:00
Signals.inc Only print the stack trace if it was requested. Previously, any call into 2006-06-16 00:00:57 +00:00
TimeValue.inc comment the hpux bit 2005-05-16 06:59:53 +00:00
Unix.h Change AllocateRWX/DeallocateRWX to not throw an exception. 2006-07-07 17:32:37 +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.