OSchip
/
llvm-project
mirror of https://github.com/THU-DSP-LAB/llvm-project.git
13
0
Fork 6
Code Issues Packages Projects Releases Wiki Activity
llvm-project/llvm/lib/Support/Unix
History
Tim Northover b89bcefa62 Reapply: Add an error message to the default SIGPIPE handler 
UNIX03 conformance requires utilities to flush stdout before exiting and raise
an error if writing fails. Flushing already happens on a call to exit
and thus automatically on a return from main. Write failure is then
detected by LLVM's default SIGPIPE handler. The handler already exits with
a non-zero code, but conformance additionally requires an error message.

First reapply attempt I hadn't noticed the test had changed, hopefully this
goes better.
 		2022-06-09 20:13:45 +01:00
..
COM.inc [llvm] Use = default (NFC) 2022-02-06 22:18:35 -08:00
DynamicLibrary.inc
…
Host.inc
…
Memory.inc Cleanup include: TableGen 2022-03-11 11:41:32 +01:00
Path.inc LLVM Driver Multicall tool 2022-06-06 04:27:32 +00:00
Process.inc [llvm/Support] Fallback to $TERM if terminfo has no "colors" capability 2022-05-18 18:22:46 -07:00
Program.inc [llvm] Use StringRef::contains (NFC) 2021-10-23 08:45:27 -07:00
README.txt
…
Signals.inc Reapply: Add an error message to the default SIGPIPE handler 2022-06-09 20:13:45 +01:00
ThreadLocal.inc [Support] Remove unused/uncompilable !HAVE_PTHREAD_GETSPECIFIC code path 2022-04-11 14:20:33 -07:00
Threading.inc Add ThreadPriority::Low, and use QoS class Utility on Mac 2022-05-16 10:01:49 +02:00
Unix.h [llvm] Unix.h - Replace report_fatal_error(std::string) with report_fatal_error(Twine) 2021-10-06 12:13:40 +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.