maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/compiler-rt/test/profile/instrprof-write-file-only.c

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

36 lines
1.2 KiB
C
Raw Normal View History

InstrProf: Test the functions in the runtime Check that the profile runtime works as expected. This tests the functions that are meant to be available to advanced users. In particular, check that the `atexit()` hook can be disabled by defining a custom `__llvm_profile_runtime` variable, that the libc dependencies are optional, and that the various functions for writing out files work for basic cases. llvm-svn: 208460
2014-05-10 07:14:58 +08:00
// RUN: %clang_profgen -o %t -O3 %s
// RUN: env LLVM_PROFILE_FILE=%t.profraw %run %t
// RUN: llvm-profdata merge -o %t.profdata %t.profraw
// RUN: %clang_profuse=%t.profdata -o - -S -emit-llvm %s | FileCheck %s
int __llvm_profile_runtime = 0;
profile: explicitly initialize file name in the test The instrprofile-write-file-only test was failing on the builtbots. The runtime library initialization is explicitly being discarded to avoid the atexit hook. However, this would also prevent the filename from being initialized. Thus, when the write file was invoked, the filename would not be setup, and the test would fail as the profiling data would never be written out. Explicitly initialize the filename to ensure that the data is written out when requested. This should hopefully finally get the build bots all green again. llvm-svn: 209099
2014-05-19 04:05:35 +08:00
void __llvm_profile_initialize_file(void);
InstrProf: Test the functions in the runtime Check that the profile runtime works as expected. This tests the functions that are meant to be available to advanced users. In particular, check that the `atexit()` hook can be disabled by defining a custom `__llvm_profile_runtime` variable, that the libc dependencies are optional, and that the various functions for writing out files work for basic cases. llvm-svn: 208460
2014-05-10 07:14:58 +08:00
int __llvm_profile_write_file(void);
void __llvm_profile_set_filename(const char *);
int foo(int);
int main(int argc, const char *argv[]) {
InstrProf: support PowerPC64 Summary: I don't know anything about profiling but it seems to work out of the box on PowerPC64. At least "make check-profile" works. A few tests needed tweaking because PowerPC64 IR declares main with "define signext i32 @main" instead of just "define i32 @main". This also fixes the asan asan_and_llvm_coverage_test test, which compiles with -coverage so requires that a profiling version of libclang_rt has been built. Reviewers: dexonsmith, kcc, samsonov Reviewed By: samsonov Subscribers: samsonov, llvm-commits Differential Revision: http://reviews.llvm.org/D6233 llvm-svn: 221877
2014-11-13 17:24:32 +08:00
// CHECK-LABEL: define {{.*}} @main(
profile: Robustify instrprof tests Change these tests not to rely on the exact metadata numbers the profile data gets. llvm-svn: 222279
2014-11-19 07:03:14 +08:00
// CHECK: br i1 %{{.*}}, label %{{.*}}, label %{{.*}}, !prof ![[PD1:[0-9]+]]
[libprofile] Adjust dummy condition to be more forgiving. On PS4, we have to fake environment variables by passing extra command line arguments, so the dummy test `argc > 1` was failing. The condition is just a dummy condition that the compiler can't fold away, so the number is arbitrary as long as the condition is false. Increase the number it compares against. llvm-svn: 264491
2016-03-26 12:01:57 +08:00
if (argc > 42)
InstrProf: Test the functions in the runtime Check that the profile runtime works as expected. This tests the functions that are meant to be available to advanced users. In particular, check that the `atexit()` hook can be disabled by defining a custom `__llvm_profile_runtime` variable, that the libc dependencies are optional, and that the various functions for writing out files work for basic cases. llvm-svn: 208460
2014-05-10 07:14:58 +08:00
return 1;
profile: explicitly initialize file name in the test The instrprofile-write-file-only test was failing on the builtbots. The runtime library initialization is explicitly being discarded to avoid the atexit hook. However, this would also prevent the filename from being initialized. Thus, when the write file was invoked, the filename would not be setup, and the test would fail as the profiling data would never be written out. Explicitly initialize the filename to ensure that the data is written out when requested. This should hopefully finally get the build bots all green again. llvm-svn: 209099
2014-05-19 04:05:35 +08:00
// Since the runtime has been suppressed, initialize the file name, as the
// writing will fail below as the file name has not been specified.
__llvm_profile_initialize_file();
InstrProf: Test the functions in the runtime Check that the profile runtime works as expected. This tests the functions that are meant to be available to advanced users. In particular, check that the `atexit()` hook can be disabled by defining a custom `__llvm_profile_runtime` variable, that the libc dependencies are optional, and that the various functions for writing out files work for basic cases. llvm-svn: 208460
2014-05-10 07:14:58 +08:00
// Write out the profile.
__llvm_profile_write_file();
// Change the profile.
return foo(0);
}
int foo(int X) {
// There should be no profiling information for @foo, since it was called
Fix typos llvm-svn: 208841
2014-05-15 10:22:34 +08:00
// after the profile was written (and the atexit was suppressed by defining
InstrProf: Test the functions in the runtime Check that the profile runtime works as expected. This tests the functions that are meant to be available to advanced users. In particular, check that the `atexit()` hook can be disabled by defining a custom `__llvm_profile_runtime` variable, that the libc dependencies are optional, and that the various functions for writing out files work for basic cases. llvm-svn: 208460
2014-05-10 07:14:58 +08:00
// profile_runtime).
InstrProf: support PowerPC64 Summary: I don't know anything about profiling but it seems to work out of the box on PowerPC64. At least "make check-profile" works. A few tests needed tweaking because PowerPC64 IR declares main with "define signext i32 @main" instead of just "define i32 @main". This also fixes the asan asan_and_llvm_coverage_test test, which compiles with -coverage so requires that a profiling version of libclang_rt has been built. Reviewers: dexonsmith, kcc, samsonov Reviewed By: samsonov Subscribers: samsonov, llvm-commits Differential Revision: http://reviews.llvm.org/D6233 llvm-svn: 221877
2014-11-13 17:24:32 +08:00
// CHECK-LABEL: define {{.*}} @foo(
InstrProf: Test the functions in the runtime Check that the profile runtime works as expected. This tests the functions that are meant to be available to advanced users. In particular, check that the `atexit()` hook can be disabled by defining a custom `__llvm_profile_runtime` variable, that the libc dependencies are optional, and that the various functions for writing out files work for basic cases. llvm-svn: 208460
2014-05-10 07:14:58 +08:00
// CHECK: br i1 %{{.*}}, label %{{.*}}, label %{{[^,]+$}}
return X <= 0 ? -X : X;
}
Use uint64_t for branch weights instead of uint32_t CallInst::updateProfWeight() creates branch_weights with i64 instead of i32. To be more consistent everywhere and remove lots of casts from uint64_t to uint32_t, use i64 for branch_weights. Reviewed By: davidxl Differential Revision: https://reviews.llvm.org/D88609
2020-10-01 03:11:46 +08:00
// CHECK: ![[PD1]] = !{!"branch_weights", i64 1, i64 2}