summaryrefslogtreecommitdiffstats
path: root/clang/docs/SourceBasedCodeCoverage.rst
diff options
context:
space:
mode:
authorVedant Kumar <vsk@apple.com>2017-06-19 21:26:04 +0000
committerVedant Kumar <vsk@apple.com>2017-06-19 21:26:04 +0000
commit1c5f312c707f0c629dc0f06b8c13b64c3dc1a1ad (patch)
tree235c24659922080ad58f3e46b9451ba962cf2ba0 /clang/docs/SourceBasedCodeCoverage.rst
parent0d5ec1170274134d266b5c777fd9d878390a4d18 (diff)
downloadbcm5719-llvm-1c5f312c707f0c629dc0f06b8c13b64c3dc1a1ad.tar.gz
bcm5719-llvm-1c5f312c707f0c629dc0f06b8c13b64c3dc1a1ad.zip
[docs] Coverage: Improve the wording a bit
llvm-svn: 305745
Diffstat (limited to 'clang/docs/SourceBasedCodeCoverage.rst')
-rw-r--r--clang/docs/SourceBasedCodeCoverage.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/clang/docs/SourceBasedCodeCoverage.rst b/clang/docs/SourceBasedCodeCoverage.rst
index c38a00386d6..805c9879480 100644
--- a/clang/docs/SourceBasedCodeCoverage.rst
+++ b/clang/docs/SourceBasedCodeCoverage.rst
@@ -275,9 +275,9 @@ Drawbacks and limitations
=========================
* Prior to version 2.26, the GNU binutils BFD linker is not able link programs
- with coverage enabled when the ``--gc-sections`` is enabled. The suggested
- workaround is to either upgrade to a newer version of BFD, or to use the Gold
- linker.
+ compiled with ``-fcoverage-mapping`` in its ``--gc-sections`` mode. Possible
+ workarounds include disabling ``--gc-sections``, upgrading to a newer version
+ of BFD, or using the Gold linker.
* Code coverage does not handle unpredictable changes in control flow or stack
unwinding in the presence of exceptions precisely. Consider the following
OpenPOWER on IntegriCloud