clang-p2996

Files

Dimitry Andric 4043373e84 Fix DynamicLibraryTest.cpp on FreeBSD and NetBSD

Summary:

After rL301562, on FreeBSD the DynamicLibrary unittests fail, because
the test uses getMainExecutable("DynamicLibraryTests", Ptr), and since
the path does not contain any slashes, retrieving the main executable
will not work.

Reimplement getMainExecutable() for FreeBSD and NetBSD using sysctl(3),
which is more reliable than fiddling with relative or absolute paths.

Also add retrieval of the original argv[] from the GoogleTest framework,
to use as a fallback for other OSes.

Reviewers: emaste, marsupial, hans, krytarowski

Reviewed By: krytarowski

Subscribers: krytarowski, llvm-commits

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

llvm-svn: 303015

2017-05-14 18:35:38 +00:00

COM.inc

…

DynamicLibrary.inc

fix build on Cygwin

2017-05-05 16:08:22 +00:00

Host.inc

…

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

Fix DynamicLibraryTest.cpp on FreeBSD and NetBSD

2017-05-14 18:35:38 +00:00

Process.inc

Remove spurious cast of nullptr. NFC.

2017-05-11 08:53:00 +00:00

Program.inc

…

README.txt

…

RWMutex.inc

…

Signals.inc

Fix detection of backtrace() availability on FreeBSD

2017-04-12 13:51:00 +00:00

Threading.inc

Try to fix thread name truncation on non-Windows.

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

ThreadLocal.inc

…

Unix.h

Remove TimeValue usage from llvm/Support

2016-10-24 10:59:17 +00: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.