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
Edwin Vane 44338e00f8 Fix gcc/printf/ISO C++ warning 
Remove the use of the 't' length modifier to avoid a gcc warning. Based
on usage, 32 bits of precision is good enough for printing a stack
offset for a stack trace.

't' length modifier isn't in C++03 but it *is* in C++11. Added a FIXME
to reintroduce once LLVM makes the switch to C++11.

Reviewer: gribozavr
llvm-svn: 173711
 		2013-01-28 19:34:42 +00:00
..
Host.inc revert r147542 after comments from Joerg Sonnenberger 2012-01-05 18:28:46 +00:00
Memory.inc Go ahead and get rid of the old page size interface and convert all the 2012-12-31 23:31:56 +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 Fix a race condition in llvm::sys::path::unique_file: when we end up 2013-01-10 01:58:46 +00:00
Process.inc Eric thought that Darwin was right to use -1 consistently rather than 2013-01-05 00:42:50 +00:00
Program.inc Remove an unused method on Program. 2012-12-31 23:44:47 +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 Fix gcc/printf/ISO C++ warning 2013-01-28 19:34:42 +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
…
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.