r271902 - [docs] Clarify limitations section of SourceBasedCodeCoverage.rst
Vedant Kumar via cfe-commits
cfe-commits at lists.llvm.org
Mon Jun 6 08:44:41 PDT 2016
Author: vedantk
Date: Mon Jun 6 10:44:40 2016
New Revision: 271902
URL: http://llvm.org/viewvc/llvm-project?rev=271902&view=rev
Log:
[docs] Clarify limitations section of SourceBasedCodeCoverage.rst
Mention that the code coverage tool becomes less precise whenever
unpredictable changes in control flow occur.
Thanks to Sean Silva for pointing this out!
Modified:
cfe/trunk/docs/SourceBasedCodeCoverage.rst
Modified: cfe/trunk/docs/SourceBasedCodeCoverage.rst
URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/docs/SourceBasedCodeCoverage.rst?rev=271902&r1=271901&r2=271902&view=diff
==============================================================================
--- cfe/trunk/docs/SourceBasedCodeCoverage.rst (original)
+++ cfe/trunk/docs/SourceBasedCodeCoverage.rst Mon Jun 6 10:44:40 2016
@@ -188,8 +188,9 @@ Format compatibility guarantees
Drawbacks and limitations
=========================
-* Code coverage does not handle stack unwinding in the presence of uncaught
- exceptions precisely. Consider the following function:
+* Code coverage does not handle unpredictable changes in control flow or stack
+ unwinding in the presence of exceptions precisely. Consider the following
+ function:
.. code-block:: cpp
@@ -198,6 +199,6 @@ Drawbacks and limitations
return 0;
}
- If the function ``may_throw()`` propagates an exception into ``f``, the code
+ If the call to ``may_throw()`` propagates an exception into ``f``, the code
coverage tool may mark the ``return`` statement as executed even though it is
- not.
+ not. A call to ``longjmp()`` can have similar effects.
More information about the cfe-commits
mailing list