maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/lib/Support/Unix
History
Rafael Espindola 9da91a0e03 Instead friending status, provide windows and posix constructors to file_status. 
This opens the way of having static helpers in the .inc files that can
construct a file_status.

llvm-svn: 186376
 		2013-07-16 02:55:33 +00:00
..
Host.inc revert r147542 after comments from Joerg Sonnenberger 2012-01-05 18:28:46 +00:00
Memory.inc Remove declaration of __clear_cache for __APPLE__. <rdar://problem/13924072> 2013-05-19 20:33:51 +00:00
Mutex.inc Now to chant the magical incantation that will exorcise the System library 2010-11-29 19:44:50 +00:00
Path.inc Instead friending status, provide windows and posix constructors to file_status. 2013-07-16 02:55:33 +00:00
Process.inc Remove MSan hack that is no longer needed. 2013-06-20 14:19:10 +00:00
Program.inc Replace use of PathV1.h in Program.cpp. 2013-06-14 19:38:45 +00:00
README.txt
…
RWMutex.inc Now to chant the magical incantation that will exorcise the System library 2010-11-29 19:44:50 +00:00
Signals.inc Revert part of 186302 to fix buildbots. 2013-07-15 04:37:54 +00:00
ThreadLocal.inc Now to chant the magical incantation that will exorcise the System library 2010-11-29 19:44:50 +00:00
TimeValue.inc Fix a FIXME about the format and add a test. 2013-07-11 15:35:23 +00:00
Unix.h Sort includes for all of the .h files under the 'lib' tree. These were 2012-12-04 07:12:27 +00:00
Watchdog.inc Add a new watchdog timer interface. The interface does not permit handling timeouts, so 2013-03-26 01:27:52 +00:00
system_error.inc Now to chant the magical incantation that will exorcise the System library 2010-11-29 19:44:50 +00:00

README.txt 

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