RPCSX/llvm
1
0
Fork 0
mirror of https://github.com/RPCSX/llvm.git synced 2024-12-02 00:36:36 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
39253260b9
llvm/lib/System/Unix
History
Chris Lattner 39253260b9 Fix a bug where the bcreader could crash on .bc files that were an exact 
multiple of the page size, due to a bug in MappedFile


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@36980 91177308-0d34-0410-b5e6-96231b3b80d8
2007-05-11 00:00:27 +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 Fix a bug where the bcreader could crash on .bc files that were an exact 2007-05-11 00:00:27 +00:00
Memory.inc For PR797: 2006-08-23 20:34:57 +00:00
Mutex.inc Eliminate "control reaches end of non-void function" warnings. 2006-12-05 17:53:26 +00:00
Path.inc pull some win32 code into common code, add bitcode identification support. 2007-05-06 05:32:21 +00:00
Process.inc Use new config.h macro 2006-09-14 06:21:59 +00:00
Program.inc Cygwin doesn't have the RSS_LIMIT for get/setrlimit. 2007-04-23 07:22:51 +00:00
README.txt Fix a typo. 2004-08-26 07:43:33 +00:00
Signals.inc For PR1291: 2007-04-07 18:52:17 +00:00
TimeValue.inc Don't throw needlessly. Failure of gettimeofday is *very* unlinkely so 2006-08-22 17:38:44 +00:00
Unix.h For PR797: 2006-08-25 21:37:17 +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.