3125af2b6b
Mingw toolchains implicitly add an .exe suffix if the output linked file doesn't have a suffix. In many cases the extra suffix doesn't cause any issues, but in some tests, this discrepancy between expected output file name and actual output file does affect the tests. In one test, a rm command fails to remove the executable since it doesn't have the expected name. By failing to remove the executable, the later llvm-profdata command tries to read the executable as if it was a profile data file. In another test, when the Python executor executes commands, it can resolve executable names without the extra .exe suffix for absolute paths (when most binaries are executed as e.g. "%t/foo"), but it fails to resolve the executables for relative paths such as "./foo". Making the paths absolute by using %t here shouldn't affect what the test tries to validate. Differential Revision: https://reviews.llvm.org/D148169
23 lines
998 B
C
23 lines
998 B
C
// RUN: rm -rf %t
|
|
// RUN: mkdir -p %t
|
|
// RUN: cd %t
|
|
// RUN: %clang_profgen -o %t/binary %s
|
|
//
|
|
// Check that a dir separator is appended after %t is subsituted.
|
|
// RUN: env TMPDIR="%t" LLVM_PROFILE_FILE="%%traw1.profraw" %run %t/binary
|
|
// RUN: llvm-profdata show ./raw1.profraw | FileCheck %s -check-prefix TMPDIR
|
|
//
|
|
// Check that substitution works even if a redundant dir separator is added.
|
|
// RUN: env TMPDIR="%t" LLVM_PROFILE_FILE="%%t/raw2.profraw" %run %t/binary
|
|
// RUN: llvm-profdata show ./raw2.profraw | FileCheck %s -check-prefix TMPDIR
|
|
//
|
|
// Check that we fall back to the default path if TMPDIR is missing.
|
|
// RUN: env -u TMPDIR LLVM_PROFILE_FILE="%%t/raw3.profraw" %run %t/binary 2>&1 | FileCheck %s -check-prefix MISSING
|
|
// RUN: llvm-profdata show ./default.profraw | FileCheck %s -check-prefix TMPDIR
|
|
|
|
// TMPDIR: Maximum function count: 1
|
|
|
|
// MISSING: Unable to get the TMPDIR environment variable, referenced in {{.*}}raw3.profraw. Using the default path.
|
|
|
|
int main() { return 0; }
|