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
Tim Northover 7b53a45e14 Revert "Add an error message to the default SIGPIPE handler" 
It broke a PPC bot, for not immediately obvious reasons.
 		2022-05-12 08:31:20 +01:00
..
COM.inc [llvm] Use = default (NFC) 2022-02-06 22:18:35 -08:00
DynamicLibrary.inc
…
Host.inc
…
Memory.inc Cleanup include: TableGen 2022-03-11 11:41:32 +01:00
Path.inc [Support] Skip attempts to access /proc/self/fd on FreeBSD 2022-03-27 20:19:41 +02:00
Process.inc [llvm] Replace LLVM_ATTRIBUTE_NORETURN with C++11 [[noreturn]] 2021-07-28 09:31:14 -07:00
Program.inc [llvm] Use StringRef::contains (NFC) 2021-10-23 08:45:27 -07:00
README.txt
…
Signals.inc Revert "Add an error message to the default SIGPIPE handler" 2022-05-12 08:31:20 +01:00
ThreadLocal.inc [Support] Remove unused/uncompilable !HAVE_PTHREAD_GETSPECIFIC code path 2022-04-11 14:20:33 -07:00
Threading.inc
…
Unix.h [llvm] Unix.h - Replace report_fatal_error(std::string) with report_fatal_error(Twine) 2021-10-06 12:13:40 +01:00
Watchdog.inc
…

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.