llvm-project/llvm/lib/Support/Unix
Argyrios Kyrtzidis eed2dc5769 [PathV2] In llvm::sys::fs::unique_file, make sure it doesn't fall into an infinite loop by constantly trying
to create the parent path.

This can happen if the path is a relative filename and the current directory was removed.
Thanks to Daniel D. for the hint in fixing it.

llvm-svn: 176226
2013-02-28 00:38:19 +00:00
..
Host.inc revert r147542 after comments from Joerg Sonnenberger 2012-01-05 18:28:46 +00:00
Memory.inc Add comment in Memory.inc explaining r175646. 2013-02-20 19:25:09 +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 The assumption that /proc/self/exe always exists is incorrect. 2012-09-26 08:30:35 +00:00
PathV2.inc [PathV2] In llvm::sys::fs::unique_file, make sure it doesn't fall into an infinite loop by constantly trying 2013-02-28 00:38:19 +00:00
Process.inc Workaround an MSan false positive. 2013-02-14 12:18:32 +00:00
Program.inc More MSan/ASan annotations. 2013-02-04 07:03:24 +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 Rewrite comments. 2013-02-20 19:28:46 +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 initialization-order bug in llvm::Support::TimeValue. TimeValue::now() is explicitly called during module initialization of lib/Support/Process.cpp. It reads the field of global object PosixZeroTime, which is not guaranteed to be initialized at this point. Found by AddressSanitizer with -fsanitize=init-order option. 2013-02-19 11:35:39 +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
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.