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

35 lines
1.5 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
// <rdar://problem/12843084>
int test1(int a) {
switch (a % 2) {
case 0:
++a;
case 1:
a /= 2;
}
return a;
}
// Check that the noredzone flag is set on the generated functions.
Attempt to clean up tests for non-X86 platforms. llvm-svn: 175652
2013-02-21 03:30:01 +08:00
// CHECK: void @__llvm_gcov_indirect_counter_increment(i32* %{{.*}}, i64** %{{.*}}) unnamed_addr [[NRZ:#[0-9]+]]
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
// Inside llvm_gcov_writeout, check that -coverage-no-function-names-in-data
// passes null as the function name.
Attempt to clean up tests for non-X86 platforms. llvm-svn: 175652
2013-02-21 03:30:01 +08:00
// CHECK: void @__llvm_gcov_writeout() unnamed_addr [[NRZ]]
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
// CHECK: call void @llvm_gcda_emit_function({{.*}}, i8* getelementptr {{.*}}, {{.*}})
// WITHOUTNAMES: void @__llvm_gcov_writeout() unnamed_addr
// WITHOUTNAMES: call void @llvm_gcda_emit_function({{.*}}, i8* null, {{.*}})
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]+}}}