Use thread-safe statics to avoid a static constructor here.  This isn't thread-safe on MSVC, but we don't
support threaded LLVM there anyways.

llvm-svn: 119718

llvm-svn: 119433

The system API's will be shifted over to returning an error_code, and returning
other return values as out parameters to the function.

Code that needs to check error conditions will use the errc enum values which
are the same as the posix_errno defines (EBADF, E2BIG, etc...), and are
compatable with the error codes in WinError.h due to some magic in system_error.

An example would be:

if (error_code ec = KillEvil("Java")) { // error_code can be converted to bool.
  handle_error(ec);
}

llvm-svn: 119360

llvm-svn: 118683

llvm-svn: 118681

Win32/Process.inc: [PR8527] Process::FileDescriptorIsDisplayed(fd) should not check by FILE_TYPE_CHAR. It must be better to check it with Console API.

The special file "NUL" is FILE_TYPE_CHAR with GetFileType(h). It was treated as display device and discarding output to NUL had failed. (eg. opt -o nul)

llvm-svn: 118678

llvm-svn: 118507

llvm-svn: 118506

llvm-svn: 118505

llvm-svn: 118504

llvm-svn: 118503

llvm-svn: 118502

llvm-svn: 118501

llvm-svn: 118463

llvm-svn: 118442

llvm-svn: 118367

 - Primarily useful for running some code with a specified stack size, when
   pthreads are available.

llvm-svn: 118222

llvm-svn: 118128

llvm-svn: 118127

limits on their own.

llvm-svn: 118113

llvm-svn: 118110

llvm-svn: 118106

llvm-svn: 118105

llvm-svn: 118102

llvm-svn: 118096

Additionally, move the implementation of appendSuffix to Path.cpp: it is
platform-independent.

llvm-svn: 118089

llvm-svn: 118086

llvm-svn: 118058

This allows using GetDLLSuffix() with appendSuffix().

llvm-svn: 118051

This makes its behaviour more consistent across platforms.

llvm-svn: 118048

llvm-svn: 118045

llvm-svn: 118042

llvm-svn: 117666

being not found from the file being not executable. 

llvm-svn: 117664

executing the child process and abnormal child process termination.

llvm-svn: 117661

which contains slashes is inconsistent with the meaning of PATH on
Unix-type platforms, and pretty surprising.

If the user has given a specific path to execute and we can't
execute it, we should fail and say why.  (Apparently the new
posix_spawn code doesn't always say why, but that's a separate
issue.)

llvm-svn: 117596

Original commit message:

    On "Unix", if Program::FindProgramByName is given a name containing
    slashes, just go with it, regardless of whether it looks like it will
    be executable. This follows the behavior of sh(1) more closely.

It's better when behaviour is consistent between platforms. This change also
makes FindExecutable() behave as expected on unix-likes (before this commit, it
used to always succeed).

llvm-svn: 117582

llvm-svn: 117581

llvm-svn: 117538

llvm-svn: 117443