shylie/llvm-project
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
llvm-project/llvm/lib/Support/Unix
History
Benjamin Kramer adcd026838 Make llvm::StringRef to std::string conversions explicit. 
This is how it should've been and brings it more in line with
std::string_view. There should be no functional change here.

This is mostly mechanical from a custom clang-tidy check, with a lot of
manual fixups. It uncovers a lot of minor inefficiencies.

This doesn't actually modify StringRef yet, I'll do that in a follow-up.
2020-01-28 23:25:25 +01: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 0697bcb66f1d82f2fd447e9d13b74d141c3ce085
2020-01-24 18:32:54 -08:00
Path.inc
Avoid duplicate exe_path definition on recent FreeBSD
2019-11-18 08:51:22 -05:00
Process.inc
[Support] Replace sys::Mutex with their standard equivalents.
2019-08-19 19:49:57 +00: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
Threading.inc
Reland "[Support] Add a way to run a function on a detached thread""
2019-10-23 15:51:44 +02:00
ThreadLocal.inc
Update the file headers across all of the LLVM projects in the monorepo
2019-01-19 08:50:56 +00:00
Unix.h
Reland "[Support] Add a way to run a function on a detached thread""
2019-10-23 15:51:44 +02: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.