maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/lib/System/Unix
History
Jeffrey Yasskin c4e3f05380 Fix a false-positive memory leak in code using RemoveFileOnSignal(). Because 
libstdc++'s std::string class points to the interior of an allocation, valgrind
reports strings still alive at program termination as possible leaks.  I didn't
use a ManagedStatic for this because System can't depend on Support.

llvm-svn: 98716
 		2010-03-17 07:08:12 +00:00
..
Alarm.inc Fix a bunch of namespace pollution. 2009-08-07 01:32:21 +00:00
Host.inc Improve llvm::getHostTriple for some cases where the LLVM_HOSTTRIPLE is not 2009-09-03 01:10:13 +00:00
Memory.inc Move DataTypes.h to include/llvm/System, update all users. This breaks the last 2009-10-26 01:35:46 +00:00
Mutex.inc Insert a SmartMutex templated class into the class hierarchy, which takes a template parameter specifying whether this mutex 2009-06-18 17:53:17 +00:00
Path.inc Make Path use StringRef instead of std::string where possible. 2009-12-17 21:02:39 +00:00
Process.inc move a few more symbols to .rodata 2009-12-23 17:48:10 +00:00
Program.inc don't forget to close a FD on an error condition, found by 2010-03-14 23:16:45 +00:00
README.txt
…
RWMutex.inc Give RWMutex the SmartRWMutex treatment too. 2009-06-18 18:26:15 +00:00
Signals.inc Fix a false-positive memory leak in code using RemoveFileOnSignal(). Because 2010-03-17 07:08:12 +00:00
ThreadLocal.inc Fix compilation without pthreads. 2009-06-26 08:48:03 +00:00
TimeValue.inc Fix TimeValue::now() on Unix. 2010-01-22 15:51:31 +00:00
Unix.h Add a portable strerror*() wrapper, llvm::sys::StrError(). This includes the 2009-07-01 18:11:20 +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.