llvm-project

History

Alexandre Ganea 336ab2d51d [Support] On Windows, take the affinity mask into account

The number of hardware threads available to a ThreadPool can be limited if setting an affinity mask.
For example:

> start /B /AFFINITY 0xF lld-link.exe ...

Would let LLD only use 4 hyper-threads.

Previously, there was an outstanding issue on Windows Server 2019 on dual-CPU machines, which was preventing from using both CPU sockets. In normal conditions, when no affinity mask was set, ProcessorGroup::AllThreads was different from ProcessorGroup::UsableThreads. The previous code in llvm/lib/Support/Windows/Threading.inc L201 was improperly assuming those two values to be equal, and consequently was limiting the execution to only one CPU socket.

Differential Revision: https://reviews.llvm.org/D92419

2021-01-13 21:00:09 -05:00

COM.inc

…

DynamicLibrary.inc

…

Host.inc

Make llvm::StringRef to std::string conversions explicit.

2020-01-28 23:25:25 +01:00

Memory.inc

Fix header includes after 0697bcb66f1d82f2fd447e9d13b74d141c3ce085

2020-01-24 18:32:54 -08:00

Path.inc

[llvm] [Support] Fix segv if argv0 is null in getMainExecutable()

2020-11-09 11:35:11 +01:00

Process.inc

[CMake] Use find_library for ncurses

2020-08-31 20:06:21 -07:00

Program.inc

[Support] On Windows, take the affinity mask into account

2021-01-13 21:00:09 -05:00

README.txt

…

Signals.inc

[Signal] Re-raise SIGPIPE if the handler is uninstalled

2021-01-08 11:13:43 -08:00

Threading.inc

Implement computeHostNumHardwareThreads() for FreeBSD

2020-11-29 00:49:39 +01:00

ThreadLocal.inc

…

Unix.h

Stop including sys/param.h from Unix.h

2020-02-25 15:35:04 +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.