[NFC] Make sure that tests use %t

As per https://llvm.org/docs/CommandGuide/lit.html#substitutions, %t is
a common substitution used for temporary file name unique to the test.
Make sure that all tests use %t instead of some arbitrary names. This is
important as otherwise tests might be re-using files generated by other
tests.

Author: banach-space

test/DuplicateBB_MergeBB_exec.ll

@@ -1,22 +1,22 @@
 ; RUN: %clang -S -emit-llvm %S/../inputs/input_for_mba.c -o - \
 ; RUN:   | opt -load %shlibdir/libRIV%shlibext -load %shlibdir/libDuplicateBB%shlibext -legacy-duplicate-bb -S -o - \
-; RUN:   | opt -load  %shlibdir/libMergeBB%shlibext -legacy-merge-bb -S -o %instrumented.ll
-; RUN: %clang %instrumented.ll -o %instrumented.bin
+; RUN:   | opt -load  %shlibdir/libMergeBB%shlibext -legacy-merge-bb -S -o %t.ll
+; RUN: %clang %t.ll -o %t.bin
 
 ; Verify that after applying DuplicaateBB + MergeBB the output generated by the
 ; input module (input_for_mba.c) doesn't change.
 
 ; The program implemented in input_for_mba.c takes for inputs and adds them up,
 ; and returns the result. So if they add up to 0, then the binary returns `0`
 ; (aka success). Verify that the obfuscation didn't violate this invariant.
-; RUN: ./%instrumented.bin 0 0 0 0
-; RUN: ./%instrumented.bin 1 2 3 -6
-; RUN: ./%instrumented.bin -13 13 -13 13
-; RUN: ./%instrumented.bin -11100 100 1000 10000
+; RUN: %t.bin 0 0 0 0
+; RUN: %t.bin 1 2 3 -6
+; RUN: %t.bin -13 13 -13 13
+; RUN: %t.bin -11100 100 1000 10000
 
 ; If the input values don't add up to 0, then the result shouldn't add to `0`.
 ; Use `not` to negate the result so that we still test for `success`.
-; RUN: not ./%instrumented.bin 0 0 0 1
-; RUN: not ./%instrumented.bin 1 2 3 -7
-; RUN: not ./%instrumented.bin 13 13 -13 13
-; RUN: not ./%instrumented.bin -11101 100 1000 10000
+; RUN: not %t.bin 0 0 0 1
+; RUN: not %t.bin 1 2 3 -7
+; RUN: not %t.bin 13 13 -13 13
+; RUN: not %t.bin -11101 100 1000 10000

test/DuplicateBB_exec.ll

@@ -1,21 +1,21 @@
 ; RUN: %clang -S -emit-llvm %S/../inputs/input_for_mba.c -o - \
-; RUN:   | opt -load %shlibdir/libRIV%shlibext -load %shlibdir/libDuplicateBB%shlibext -legacy-duplicate-bb -S -o %instrumented.ll
-; RUN: %clang %instrumented.ll -o %instrumented.bin
+; RUN:   | opt -load %shlibdir/libRIV%shlibext -load %shlibdir/libDuplicateBB%shlibext -legacy-duplicate-bb -S -o %t.ll
+; RUN: %clang %t.ll -o %t.bin
 
 ; Verify that after applying DuplicateBB the output generated by the input
 ; module (input_for_mba.c) doesn't change.
 
 ; The program implemented in input_for_mba.c takes for inputs and adds them up,
 ; and returns the result. So if they add up to 0, then the binary returns `0`
 ; (aka success). Verify that the obfuscation didn't violate this invariant.
-; RUN: ./%instrumented.bin 0 0 0 0
-; RUN: ./%instrumented.bin 1 2 3 -6
-; RUN: ./%instrumented.bin -13 13 -13 13
-; RUN: ./%instrumented.bin -11100 100 1000 10000
+; RUN: %t.bin 0 0 0 0
+; RUN: %t.bin 1 2 3 -6
+; RUN: %t.bin -13 13 -13 13
+; RUN: %t.bin -11100 100 1000 10000
 
 ; If the input values don't add up to 0, then the result shouldn't add to `0`.
 ; Use `not` to negate the result so that we still test for `success`.
-; RUN: not ./%instrumented.bin 0 0 0 1
-; RUN: not ./%instrumented.bin 1 2 3 -7
-; RUN: not ./%instrumented.bin 13 13 -13 13
-; RUN: not ./%instrumented.bin -11101 100 1000 10000
+; RUN: not %t.bin 0 0 0 1
+; RUN: not %t.bin 1 2 3 -7
+; RUN: not %t.bin 13 13 -13 13
+; RUN: not %t.bin -11101 100 1000 10000

test/DynamicCallCounterTest1.ll

@@ -1,7 +1,7 @@
-; RUN: opt -load %shlibdir/libDynamicCallCounter%shlibext -legacy-dynamic-cc -verify %S/Inputs/CallCounterInput.ll -o instrumented.bin
-; RUN: lli ./instrumented.bin | FileCheck %s
-; RUN: opt -load-pass-plugin %shlibdir/libDynamicCallCounter%shlibext -passes=dynamic-cc -verify %S/Inputs/CallCounterInput.ll -o instrumented.bin
-; RUN: lli ./instrumented.bin | FileCheck %s
+; RUN: opt -load %shlibdir/libDynamicCallCounter%shlibext -legacy-dynamic-cc -verify %S/Inputs/CallCounterInput.ll -o %t.bin
+; RUN: lli %t.bin | FileCheck %s
+; RUN: opt -load-pass-plugin %shlibdir/libDynamicCallCounter%shlibext -passes=dynamic-cc -verify %S/Inputs/CallCounterInput.ll -o %t.bin
+; RUN: lli %t.bin | FileCheck %s
 
 ; Instrument this file with DynamicCallCounter, run it and verify that it
 ; generates the expected output.

test/MergeBB_exec.ll

@@ -1,21 +1,21 @@
 ; RUN: %clang -S -emit-llvm %S/../inputs/input_for_mba.c -o - \
-; RUN:   | opt -load  %shlibdir/libMergeBB%shlibext -legacy-merge-bb -S -o %instrumented.ll
-; RUN: %clang %instrumented.ll -o %instrumented.bin
+; RUN:   | opt -load  %shlibdir/libMergeBB%shlibext -legacy-merge-bb -S -o %t.ll
+; RUN: %clang %t.ll -o %t.bin
 
 ; Verify that after applying MergeBB the output generated by the input
 ; module (input_for_mba.c) doesn't change.
 
 ; The program implemented in input_for_mba.c takes for inputs and adds them up,
 ; and returns the result. So if they add up to 0, then the binary returns `0`
 ; (aka success). Verify that the obfuscation didn't violate this invariant.
-; RUN: ./%instrumented.bin 0 0 0 0
-; RUN: ./%instrumented.bin 1 2 3 -6
-; RUN: ./%instrumented.bin -13 13 -13 13
-; RUN: ./%instrumented.bin -11100 100 1000 10000
+; RUN: %t.bin 0 0 0 0
+; RUN: %t.bin 1 2 3 -6
+; RUN: %t.bin -13 13 -13 13
+; RUN: %t.bin -11100 100 1000 10000
 
 ; If the input values don't add up to 0, then the result shouldn't add to `0`.
 ; Use `not` to negate the result so that we still test for `success`.
-; RUN: not ./%instrumented.bin 0 0 0 1
-; RUN: not ./%instrumented.bin 1 2 3 -7
-; RUN: not ./%instrumented.bin 13 13 -13 13
-; RUN: not ./%instrumented.bin -11101 100 1000 10000
+; RUN: not %t.bin 0 0 0 1
+; RUN: not %t.bin 1 2 3 -7
+; RUN: not %t.bin 13 13 -13 13
+; RUN: not %t.bin -11101 100 1000 10000

test/inject_func_call_exec.ll

@@ -1,6 +1,6 @@
 ; RUN: %clang -c -emit-llvm %S/../inputs/input_for_hello.c -o - \
-; RUN:   | opt -load %shlibdir/libInjectFuncCall%shlibext -legacy-inject-func-call -verify -o instrumented.bin
-; RUN: not lli ./instrumented.bin | FileCheck %s
+; RUN:   | opt -load %shlibdir/libInjectFuncCall%shlibext -legacy-inject-func-call -verify -o %t.bin
+; RUN: not lli %t.bin | FileCheck %s
 
 ; This test instruments the input file (input_for_inject.c) with InjectFuncCall and runs it via lli.
 ; Below is the expected output.