maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

[docs] Add a limitations section to SourceBasedCodeCoverage.rst 

llvm-svn: 271544
This commit is contained in:
Vedant Kumar 2016-06-02 17:19:45 +00:00
parent 93c99cf059
commit 553a0d62f2
1 changed files with 19 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
clang/docs/SourceBasedCodeCoverage.rst
View File

@ -165,9 +165,9 @@ A few final notes:
indexed profiles. To combine profiling data from multiple runs of a program, indexed profiles. To combine profiling data from multiple runs of a program,
try e.g: try e.g:
.. code-block:: console .. code-block:: console
% llvm-profdata merge -sparse foo1.profraw foo2.profdata -o foo3.profdata % llvm-profdata merge -sparse foo1.profraw foo2.profdata -o foo3.profdata
Format compatibility guarantees Format compatibility guarantees
=============================== ===============================
@ -184,3 +184,20 @@ Format compatibility guarantees
* There is a third format in play: the format of the coverage mappings emitted * There is a third format in play: the format of the coverage mappings emitted
into instrumented binaries. Tools must retain **backwards** compatibility into instrumented binaries. Tools must retain **backwards** compatibility
with these formats. These formats are not forwards-compatible. with these formats. These formats are not forwards-compatible.
Drawbacks and limitations
=========================
* Code coverage does not handle stack unwinding in the presence of uncaught
exceptions precisely. Consider the following function:
.. code-block:: cpp
int f() {
may_throw();
return 0;
}
If the function ``may_throw()`` propagates an exception into ``f``, the code
coverage tool may mark the ``return`` statement as executed even though it is
not.