6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-11-15 04:08:07 +00:00
Code Issues Projects Releases Wiki Activity
9ffd19af2e
llvm-6502/lib/System/Unix
History
Chris Lattner 9ffd19af2e Implement Path::MapInFilePages/UnMapFilePages on unix, which 
provides fast MappedFile::getFile for large files.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@49034 91177308-0d34-0410-b5e6-96231b3b80d8
2008-04-01 06:16:24 +00:00
..
Alarm.inc Remove attribution from file headers, per discussion on llvmdev. 2007-12-29 20:36:04 +00:00
MappedFile.inc Implement Path::MapInFilePages/UnMapFilePages on unix, which 2008-04-01 06:16:24 +00:00
Memory.inc Revert r48676. I had plans for using it, but now it's just dead code. 2008-03-24 21:29:58 +00:00
Mutex.inc Remove attribution from file headers, per discussion on llvmdev. 2007-12-29 20:36:04 +00:00
Path.inc Implement Path::MapInFilePages/UnMapFilePages on unix, which 2008-04-01 06:16:24 +00:00
Process.inc Actually disable crash reporting on Mac OS X, returning bugpoint to speedy 2008-03-31 22:19:25 +00:00
Program.inc Set error message. 2008-02-04 20:57:54 +00:00
README.txt
Signals.inc Avoid calling array_endof in a static initializer, as it incurs 2008-03-21 23:44:21 +00:00
TimeValue.inc Remove attribution from file headers, per discussion on llvmdev. 2007-12-29 20:36:04 +00:00
Unix.h Remove attribution from file headers, per discussion on llvmdev. 2007-12-29 20:36:04 +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.