3 Commits

Author	SHA1	Message	Date
Igor Kudrin	24466cded7	[Coverage] Ensure that coverage mapping data has an expected alignment in 'covmapping' files. ... Coverage mapping data is organized in a sequence of blocks, each of which is expected to be aligned by 8 bytes. This feature is used when reading those blocks, see VersionedCovMapFuncRecordReader::readFunctionRecords(). If a misaligned covearge mapping data has more than one block, it causes llvm-cov to fail. Differential Revision: http://reviews.llvm.org/D20285 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@269887 91177308-0d34-0410-b5e6-96231b3b80d8	2016-05-18 07:43:27 +00:00
Justin Bogner	a378f917af	InstrProf: Remove CoverageMapping::HasCodeBefore, it isn't used ... It's not entirely clear to me what this field was meant for, but it's always false. Remove it. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@228034 91177308-0d34-0410-b5e6-96231b3b80d8	2015-02-03 21:35:36 +00:00
Alex Lorenz	6c7a6a1ba2	llvm-cov: add code coverage tool that's based on coverage mapping format and clang's pgo. ... This commit expands llvm-cov's functionality by adding support for a new code coverage tool that uses LLVM's coverage mapping format and clang's instrumentation based profiling. The gcov compatible tool can be invoked by supplying the 'gcov' command as the first argument, or by modifying the tool's name to end with 'gcov'. Differential Revision: http://reviews.llvm.org/D4445 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@216300 91177308-0d34-0410-b5e6-96231b3b80d8	2014-08-22 22:56:03 +00:00