forked from OSchip/llvm-project
727891c918
Summary: We tell the user to file a bug report on LLVM right now, and SIGPIPE isn't LLVM's fault so our error message is wrong. Allows frontends to detect SIGPIPE from writing to closed readers. This can be seen commonly from piping into head, tee, or split. Fixes PR25349, rdar://problem/14285346, b/77310947 Reviewers: jfb Reviewed By: jfb Subscribers: majnemer, kristina, llvm-commits, thakis, srhines Differential Revision: https://reviews.llvm.org/D53000 llvm-svn: 344372 |
||
|---|---|---|
| .. | ||
| COM.inc | ||
| DynamicLibrary.inc | ||
| Host.inc | ||
| Memory.inc | ||
| Mutex.inc | ||
| Path.inc | ||
| Process.inc | ||
| Program.inc | ||
| README.txt | ||
| RWMutex.inc | ||
| Signals.inc | ||
| ThreadLocal.inc | ||
| Threading.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.