llvm-project

History

Alexander Kornienko 208eecd57f Convenience/safety fix for llvm::sys::Execute(And|No)Wait

Summary:
Change the type of the Redirects parameter of llvm::sys::ExecuteAndWait,
ExecuteNoWait and other APIs that wrap them from `const StringRef **` to
`ArrayRef<Optional<StringRef>>`, which is safer and simplifies the use of these
APIs (no more local StringRef variables just to get a pointer to).

Corresponding clang changes will be posted as a separate patch.

Reviewers: bkramer

Reviewed By: bkramer

Subscribers: vsk, llvm-commits

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

llvm-svn: 313155

2017-09-13 17:03:37 +00:00

COM.inc

…

DynamicLibrary.inc

Allow clients to specify search order of DynamicLibraries.

2017-07-12 21:22:45 +00:00

Host.inc

[Support] sys::getProcessTriple should return a macOS triple using

2017-07-07 09:53:47 +00:00

Memory.inc

Implement AllocateRWX and ReleaseRWX for NetBSD

2017-06-18 16:52:32 +00:00

Mutex.inc

…

Path.inc

[Support] Remove getPathFromOpenFD, it was unused

2017-08-04 17:43:49 +00:00

Process.inc

Remove Bitrig: LLVM Changes

2017-07-21 22:48:47 +00:00

Program.inc

Convenience/safety fix for llvm::sys::Execute(And|No)Wait

2017-09-13 17:03:37 +00:00

README.txt

…

RWMutex.inc

…

Signals.inc

Sort the remaining #include lines in include/... and lib/....

2017-06-06 11:49:48 +00:00

Threading.inc

Untabify.

2017-08-28 06:47:47 +00:00

ThreadLocal.inc

…

Unix.h

…

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.