llvm-project/llvm/lib/Support/Unix
Fangrui Song 041a3557f0 [CMake] Delete HAVE_SCHED_GETAFFINITY and HAVE_CPU_COUNT
sched_getaffinity (Linux specific) has been available

* in glibc since 2002-08-08 (commit 972e719e8154eec5f543b027e2a08dfa285d55d5)
* in musl since the initial check-in.
2020-04-19 08:50:23 -07:00
..
COM.inc Update the file headers across all of the LLVM projects in the monorepo 2019-01-19 08:50:56 +00:00
DynamicLibrary.inc Update the file headers across all of the LLVM projects in the monorepo 2019-01-19 08:50:56 +00:00
Host.inc Make llvm::StringRef to std::string conversions explicit. 2020-01-28 23:25:25 +01:00
Memory.inc Fix header includes after 0697bcb66f 2020-01-24 18:32:54 -08:00
Path.inc Prefer PATH_MAX to MAXPATHLEN 2020-02-25 01:37:29 +01:00
Process.inc Introduce llvm::sys::Process::getProcessId() and adopt it 2020-04-16 15:05:37 +03:00
Program.inc Make llvm::StringRef to std::string conversions explicit. 2020-01-28 23:25:25 +01:00
README.txt
Signals.inc [Support] Optionally call signal handlers when a function wrapped by the the CrashRecoveryContext fails 2020-01-11 15:27:07 -05:00
ThreadLocal.inc Update the file headers across all of the LLVM projects in the monorepo 2019-01-19 08:50:56 +00:00
Threading.inc [CMake] Delete HAVE_SCHED_GETAFFINITY and HAVE_CPU_COUNT 2020-04-19 08:50:23 -07:00
Unix.h Stop including sys/param.h from Unix.h 2020-02-25 15:35:04 +01:00
Watchdog.inc Update the file headers across all of the LLVM projects in the monorepo 2019-01-19 08:50:56 +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.