llvm-project/llvm/lib/Support/Unix
Archibald Elliott 3c97f6cab9 [Support] Move getHostNumPhysicalCores to Threading.h
This change is focussed on simplifying `Support/Host.h` to only do
target detection. In this case, this function is close in usage to
existing functions in `Support/Threading.h`, so I moved it into there.
The function is also renamed to `llvm::get_physical_cores()` to match
the style of threading's functions.

The big change here is that now if you have threading disabled,
`llvm::get_physical_cores()` will return -1, as if it had not been able
to work out the right info. This is due to how Threading.cpp includes
OS-specific code/headers. This seems ok, as if threading is disabled,
LLVM should not need to know the number of physical cores.

Differential Revision: https://reviews.llvm.org/D137836
2022-11-29 13:14:13 +00:00
..
COM.inc [Support] Apply clang-format on .inc files. NFC. 2022-11-26 09:36:43 -05:00
DynamicLibrary.inc [Support] Apply clang-format on .inc files. NFC. 2022-11-26 09:36:43 -05:00
Host.inc
Memory.inc [Support] Apply clang-format on .inc files. NFC. 2022-11-26 09:36:43 -05:00
Path.inc [Support] Apply clang-format on .inc files. NFC. 2022-11-26 09:36:43 -05:00
Process.inc [Support] Apply clang-format on .inc files. NFC. 2022-11-26 09:36:43 -05:00
Program.inc [Support] Apply clang-format on .inc files. NFC. 2022-11-26 09:36:43 -05:00
README.txt
Signals.inc [Support] Apply clang-format on .inc files. NFC. 2022-11-26 09:36:43 -05:00
ThreadLocal.inc [Support] Apply clang-format on .inc files. NFC. 2022-11-26 09:36:43 -05:00
Threading.inc [Support] Move getHostNumPhysicalCores to Threading.h 2022-11-29 13:14:13 +00:00
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 [Support] Apply clang-format on .inc files. NFC. 2022-11-26 09:36:43 -05: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.