vitalyisaev 6ffe9e5365 YQ Connector: support managed ClickHouse 1 year ago
..
COM.inc 6ffe9e5365 YQ Connector: support managed ClickHouse 1 year ago
DynamicLibrary.inc 6ffe9e5365 YQ Connector: support managed ClickHouse 1 year ago
Host.inc 6ffe9e5365 YQ Connector: support managed ClickHouse 1 year ago
Memory.inc 6ffe9e5365 YQ Connector: support managed ClickHouse 1 year ago
Path.inc 6ffe9e5365 YQ Connector: support managed ClickHouse 1 year ago
Process.inc 6ffe9e5365 YQ Connector: support managed ClickHouse 1 year ago
Program.inc 6ffe9e5365 YQ Connector: support managed ClickHouse 1 year ago
README.txt 6ffe9e5365 YQ Connector: support managed ClickHouse 1 year ago
Signals.inc 6ffe9e5365 YQ Connector: support managed ClickHouse 1 year ago
ThreadLocal.inc 6ffe9e5365 YQ Connector: support managed ClickHouse 1 year ago
Threading.inc 6ffe9e5365 YQ Connector: support managed ClickHouse 1 year ago
Unix.h 6ffe9e5365 YQ Connector: support managed ClickHouse 1 year ago
Watchdog.inc 6ffe9e5365 YQ Connector: support managed ClickHouse 1 year ago

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.