UnstableChanges

Changes from Git (git http://labmaster3.local/git/llvm-project.git)

Summary

  1. gn build: Merge r235758 (details)
  2. gn build: (manually) merge r374606 better (details)
  3. [libFuzzer] Don't prefix absolute paths in fuchsia. (details)
Commit 92e11e6d394df8acaed857724b27f57823143a0e by llvmgnsyncbot
gn build: Merge r235758
llvm-svn: 374610
The file was modifiedllvm/utils/gn/secondary/libunwind/src/BUILD.gn
Commit 1b82fb61c18474473ea21123b9a150e1a88dddbf by nicolasweber
gn build: (manually) merge r374606 better
llvm-svn: 374611
The file was modifiedllvm/utils/gn/secondary/libunwind/src/BUILD.gn
Commit cde860a1c996b0badff5f8f10baf48df3c19d921 by jakehehrlich
[libFuzzer] Don't prefix absolute paths in fuchsia.
The ExecuteCommand function in fuchsia used to prefix the getOutputFile
for each command run with the artifact_prefix flag if it was available,
because fuchsia components don't have a writable working directory.
However, if a file with a global path is provided, fuchsia should honor
that.
An example of this is using the global /tmp directory to store stuff. In
fuchsia it ended up being translated to data///tmp, whereas we want to
make sure it is using /tmp (which is available to components using the
isolated-temp feature).
To test this I made the change, compiled fuchsia with this toolchain and
ran a fuzzer with the -fork=1 flag (that mode makes use of the /tmp
directory). I also tested that normal fuzzing workflow was not affected
by this.
Author: charco (Marco Vanotti) Differential Revision:
https://reviews.llvm.org/D68774
llvm-svn: 374612
The file was modifiedcompiler-rt/lib/fuzzer/FuzzerUtilFuchsia.cpp