llvm-project

History

Zachary Turner e48ace6a65 Add llvm::sys::fs::real_path.

LLVM already has real_path like functionality, but it is
cumbersome to use and involves clean up after (e.g. you have
to call openFileForRead, then close the resulting FD).

Furthermore, on Windows it doesn't work for directories since
opening a directory and opening a file require slightly
different flags.

So I add a simple function `real_path` which works for all
paths on all platforms and has a simple to use interface.

In doing so, I add the ability to opt in to resolving tilde
expressions (e.g. ~/foo), which are normally handled by
the shell.

Differential Revision: https://reviews.llvm.org/D30668

llvm-svn: 297483

2017-03-10 17:39:21 +00:00

COM.inc

Fix build broken by incorrect class name.

2015-04-27 17:22:30 +00:00

Host.inc

Triple: refactor redundant code.

2015-02-12 15:12:13 +00:00

Memory.inc

Correct mprotect page boundries to round up end page. Fixes PR30905.

2016-11-05 04:22:15 +00:00

Mutex.inc

…

Path.inc

Add llvm::sys::fs::real_path.

2017-03-10 17:39:21 +00:00

Process.inc

Zero-initialize chrono duration objects

2016-11-09 11:43:57 +00:00

Program.inc

Revert "Fix Clang-tidy modernize-deprecated-headers warnings in remaining files; other minor fixes."

2016-04-05 20:45:04 +00:00

README.txt

…

RWMutex.inc

…

Signals.inc

Fix LLDB Android AArch64 GCC debug info build

2017-02-02 01:17:49 +00:00

Threading.inc

Try to fix thread name truncation on non-Windows.

2017-03-04 18:53:09 +00:00

ThreadLocal.inc

Revert "Fix Clang-tidy modernize-deprecated-headers warnings in remaining files; other minor fixes."

2016-04-05 20:45:04 +00:00

Unix.h

Remove TimeValue usage from llvm/Support

2016-10-24 10:59:17 +00:00

Watchdog.inc

Revert r240137 (Fixed/added namespace ending comments using clang-tidy. NFC)

2015-06-23 09:49:53 +00:00

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.