llvm-project/llvm/test/tools/llvm-cov/Inputs/test_no_gcda.output

File './test.h'
Lines executed:0.00% of 1
./test.h:creating 'test.h.gcov'

File 'test.cpp'
Lines executed:0.00% of 38
test.cpp:creating 'test.cpp.gcov'
llvm-cov: Ignore missing .gcda files When gcov is run without gcda data, it acts as if the counts are all zero and labels the file as - to indicate that there was no data. We should do the same. llvm-svn: 200740 2014-02-04 14:41:39 +08:00			`File './test.h'`
			`Lines executed:0.00% of 1`
llvm-cov: Implement the preserve-paths flag Until now, when a path in a gcno file included a directory, we would emit our .gcov file in that directory, whereas gcov always emits the file in the current directory. In doing so, this implements gcov's strange name-mangling -p flag, which is needed to avoid clobbering files when two with the same name exist in different directories. The path mangling is a bit ugly and only handles unix-like paths, but it's simple, and it doesn't make any guesses as to how it should behave outside of what gcov documents. If we decide this should be cross platform later, we can consider the compatibility implications then. llvm-svn: 200754 2014-02-04 18:45:02 +08:00			`./test.h:creating 'test.h.gcov'`
llvm-cov: Ignore missing .gcda files When gcov is run without gcda data, it acts as if the counts are all zero and labels the file as - to indicate that there was no data. We should do the same. llvm-svn: 200740 2014-02-04 14:41:39 +08:00
[gcov] Sort file info before printing it The order in which GCOV file info is printed depends on the string hash function. This makes some GCOV tests brittle, because the tests must be updated whenever the hash function changes. Sort the filenames before printing out the file info to solve the problem. This should be relatively cheap. Differential Revision: https://reviews.llvm.org/D32512 llvm-svn: 301371 2017-04-26 08:16:10 +08:00			`File 'test.cpp'`
			`Lines executed:0.00% of 38`
			`test.cpp:creating 'test.cpp.gcov'`