maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/CodeGen/code-coverage.c

51 lines
2.2 KiB
C
Raw Normal View History

Now that the uninitialized variable has been fixed in llvm, add this test back, but remove unneeded options and fix the comment. llvm-svn: 170405
2012-12-18 11:54:29 +08:00
// RUN: %clang_cc1 -emit-llvm -disable-red-zone -femit-coverage-data %s -o - | FileCheck %s
The flag "-coverage-function-names-in-data" is actually backwards -- we do emit function names in .gcda files by default, and the flag turns that off! Rename the flag to make it match what it actually does. This keeps the default format compatible with gcc 4.2. Also add a test for this flag. llvm-svn: 177475
2013-03-20 10:14:38 +08:00
// RUN: %clang_cc1 -emit-llvm -disable-red-zone -femit-coverage-data -coverage-no-function-names-in-data %s -o - | FileCheck %s --check-prefix WITHOUTNAMES
[Coverage] Update test after r284418. We now strip coverage metadata if debug info are not present. llvm-svn: 284419
2016-10-18 04:06:32 +08:00
// RUN: %clang_cc1 -emit-llvm -disable-red-zone -femit-coverage-data -coverage-notes-file=aaa.gcno -coverage-data-file=bbb.gcda -dwarf-column-info -debug-info-kind=limited -dwarf-version=4 %s -o - | FileCheck %s --check-prefix GCOV_FILE_INFO
Now that the uninitialized variable has been fixed in llvm, add this test back, but remove unneeded options and fix the comment. llvm-svn: 170405
2012-12-18 11:54:29 +08:00
Wire up GCOV to the new pass manager GCOV in the old pass manager also strips debug info (if debug info is disabled/only produced for profiling anyway) after the GCOV pass runs. I think the strip pass hasn't been ported to the new pass manager, so it might take me a little while to wire that up. llvm-svn: 322126
2018-01-10 06:03:47 +08:00
// RUN: %clang_cc1 -emit-llvm-bc -o /dev/null -fexperimental-new-pass-manager -fdebug-pass-manager -femit-coverage-data %s 2>&1 | FileCheck --check-prefix=NEWPM %s
NewPM: Improve/fix GCOV - which needs to run early in the pass pipeline. Using a new extension point in the new PM, register GCOV at the start of the pipeline rather than the end. llvm-svn: 323167
2018-01-23 09:25:24 +08:00
// RUN: %clang_cc1 -emit-llvm-bc -o /dev/null -fexperimental-new-pass-manager -fdebug-pass-manager -femit-coverage-data -O3 %s 2>&1 | FileCheck --check-prefix=NEWPM-O3 %s
Wire up GCOV to the new pass manager GCOV in the old pass manager also strips debug info (if debug info is disabled/only produced for profiling anyway) after the GCOV pass runs. I think the strip pass hasn't been ported to the new pass manager, so it might take me a little while to wire that up. llvm-svn: 322126
2018-01-10 06:03:47 +08:00
NewPM: Improve/fix GCOV - which needs to run early in the pass pipeline. Using a new extension point in the new PM, register GCOV at the start of the pipeline rather than the end. llvm-svn: 323167
2018-01-23 09:25:24 +08:00
// NEWPM-NOT: Running pass
Wire up GCOV to the new pass manager GCOV in the old pass manager also strips debug info (if debug info is disabled/only produced for profiling anyway) after the GCOV pass runs. I think the strip pass hasn't been ported to the new pass manager, so it might take me a little while to wire that up. llvm-svn: 322126
2018-01-10 06:03:47 +08:00
// NEWPM: Running pass: GCOVProfilerPass
NewPM: Improve/fix GCOV - which needs to run early in the pass pipeline. Using a new extension point in the new PM, register GCOV at the start of the pipeline rather than the end. llvm-svn: 323167
2018-01-23 09:25:24 +08:00
// NEWPM-O3-NOT: Running pass
// NEWPM-O3: Running pass: ForceFunctionAttrsPass
// NEWPM-O3: Running pass: GCOVProfilerPass
Now that the uninitialized variable has been fixed in llvm, add this test back, but remove unneeded options and fix the comment. llvm-svn: 170405
2012-12-18 11:54:29 +08:00
int test1(int a) {
switch (a % 2) {
case 0:
++a;
case 1:
a /= 2;
}
return a;
}
[gcov] Make the CLang side coverage test work with the new instrumentation codegeneration strategy of using a data structure and a loop. Required some finesse to get the critical things being tested to surface in a nice way for FileCheck but I think this preserves the original intent of the test. llvm-svn: 331411
2018-05-03 06:57:20 +08:00
int test2(int b) {
return b * 2;
}
// Inside function emission data structure, check that
// -coverage-no-function-names-in-data uses null as the function name.
// CHECK: @__llvm_internal_gcov_emit_function_args.0 = internal unnamed_addr constant
// CHECK-SAME: { i32 {{[0-9]+}}, i8* getelementptr inbounds ({{[^,]*}}, {{[^,]*}}* @
// CHECK-SAME: { i32 {{[0-9]+}}, i8* getelementptr inbounds ({{[^,]*}}, {{[^,]*}}* @
// WITHOUTNAMES: @__llvm_internal_gcov_emit_function_args.0 = internal unnamed_addr constant
// WITHOUTNAMES-NOT: getelementptr inbounds ({{.*}}@
// WITHOUTNAMES-SAME: zeroinitializer,
// WITHOUTNAMES-NOT: getelementptr inbounds ({{.*}}@
// WITHOUTNAMES-SAME: { i32 {{[0-9]+}}, i8* null,
Now that the uninitialized variable has been fixed in llvm, add this test back, but remove unneeded options and fix the comment. llvm-svn: 170405
2012-12-18 11:54:29 +08:00
// Check that the noredzone flag is set on the generated functions.
[gcov] Update a clang test for r341977 Update test/CodeGen/code-coverage.c so that it doesn't refer to a gcov function which is no longer emitted after r341977. Fixes bot failure: http://lab.llvm.org:8011/builders/clang-ppc64be-linux/builds/23831 llvm-svn: 341985
2018-09-12 03:42:58 +08:00
// CHECK: void @__llvm_gcov_writeout() unnamed_addr [[NRZ:#[0-9]+]]
Update testcase for r177340. llvm-svn: 177344
2013-03-19 07:11:54 +08:00
// CHECK: void @__llvm_gcov_flush() unnamed_addr [[NRZ]]
Attempt to clean up tests for non-X86 platforms. llvm-svn: 175652
2013-02-21 03:30:01 +08:00
// CHECK: void @__llvm_gcov_init() unnamed_addr [[NRZ]]
Modify the tests to use attribute group references instead of listing the function attributes. llvm-svn: 175606
2013-02-20 15:22:19 +08:00
Attempt to clean up tests for non-X86 platforms. llvm-svn: 175652
2013-02-21 03:30:01 +08:00
// CHECK: attributes [[NRZ]] = { {{.*}}noredzone{{.*}} }
Add -fprofile-dir= to clang. -fprofile-dir=path allows the user to specify where .gcda files should be emitted when the program is run. In particular, this is the first flag that causes the .gcno and .o files to have different paths, LLVM is extended to support this. -fprofile-dir= does not change the file name in the .gcno (and thus where lcov looks for the source) but it does change the name in the .gcda (and thus where the runtime library writes the .gcda file). It's different from a GCOV_PREFIX because a user can observe that the GCOV_PREFIX_STRIP will strip paths off of -fprofile-dir= but not off of a supplied GCOV_PREFIX. To implement this we split -coverage-file into -coverage-data-file and -coverage-notes-file to specify the two different names. The !llvm.gcov metadata node grows from a 2-element form {string coverage-file, node dbg.cu} to 3-elements, {string coverage-notes-file, string coverage-data-file, node dbg.cu}. In the 3-element form, the file name is already "mangled" with .gcno/.gcda suffixes, while the 2-element form left that to the middle end pass. llvm-svn: 280306
2016-09-01 07:04:32 +08:00
// GCOV_FILE_INFO: !llvm.gcov = !{![[GCOV:[0-9]+]]}
// GCOV_FILE_INFO: ![[GCOV]] = !{!"aaa.gcno", !"bbb.gcda", !{{[0-9]+}}}