shylie/llvm-project
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
llvm-project/llvm/lib/Support/Unix
History
Kai Nacke ed07e1fe0f [SystemZ/ZOS] Add header file to encapsulate use of <sysexits.h> 
The non-standard header file `<sysexits.h>` provides some return values.
`EX_IOERR` is used to as a special value to signal a broken pipe to the clang driver.
On z/OS Unix System Services, this header file does not exists. This patch

- adds a check for `<sysexits.h>`, removing the dependency on `LLVM_ON_UNIX`
- adds a new header file `llvm/Support/ExitCodes`, which either includes
  `<sysexits.h>` or defines `EX_IOERR`
- updates the users of `EX_IOERR` to include the new header file

Reviewed By: hubert.reinterpretcast

Differential Revision: https://reviews.llvm.org/D83472
2020-08-26 12:44:30 -04:00
..
COM.inc
…
DynamicLibrary.inc
…
Host.inc
…
Memory.inc
…
Path.inc
[SystemZ/ZOS] Implement setLastAccessAndModificationTime()
2020-07-28 06:36:15 -04:00
Process.inc
Use find_library for ncurses
2020-08-17 19:52:52 -07:00
Program.inc
[NFC][Support] Make Unix/Program.inc separately compilable
2020-06-25 15:41:17 -04:00
README.txt
…
Signals.inc
[SystemZ/ZOS] Add header file to encapsulate use of <sysexits.h>
2020-08-26 12:44:30 -04:00
Threading.inc
call ::pthread_detach on llvm_execute_on_thread_impl
2020-07-02 14:41:05 +01: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.