Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | [docs] Coverage: Improve the wording a bit | Vedant Kumar | 2017-06-19 | 1 | -3/+3 |
| | | | | llvm-svn: 305745 | ||||
* | [docs] Coverage: document issue with the BFD linker | Vedant Kumar | 2017-06-19 | 1 | -0/+5 |
| | | | | llvm-svn: 305743 | ||||
* | [docs] coverage: Clarify which flags enable gcov-style profiling (NFC) | Vedant Kumar | 2017-02-09 | 1 | -0/+1 |
| | | | | | | | | | Point out that --coverage and -ftest-coverage, which is what most people are used to, do not enable clang's frontend based coverage pass. Suggested by Benn Bolay! llvm-svn: 294626 | ||||
* | Clarify how to forward-declare __llvm_profile symbols. | Nico Weber | 2017-01-25 | 1 | -0/+2 |
| | | | | llvm-svn: 293065 | ||||
* | [docs] Touch up the coverage docs some more | Vedant Kumar | 2016-09-22 | 1 | -22/+20 |
| | | | | llvm-svn: 282169 | ||||
* | [docs] Extend the code coverage docs some more | Vedant Kumar | 2016-09-20 | 1 | -3/+35 |
| | | | | | | | | Flesh out the section on interpreting coverage reports, mention the coverage export feature, and add notes on how to build llvm with coverage turned on. llvm-svn: 281988 | ||||
* | [docs] Touch up the code coverage doc | Vedant Kumar | 2016-09-19 | 1 | -9/+29 |
| | | | | llvm-svn: 281881 | ||||
* | [docs] Coverage: Reference the new -output-dir option | Vedant Kumar | 2016-07-28 | 1 | -1/+1 |
| | | | | llvm-svn: 277081 | ||||
* | [docs] Mention some new options in llvm-cov | Vedant Kumar | 2016-07-28 | 1 | -7/+7 |
| | | | | llvm-svn: 277080 | ||||
* | fix two typos in the doc | Sylvestre Ledru | 2016-07-02 | 1 | -1/+1 |
| | | | | llvm-svn: 274447 | ||||
* | [Docs] More warning fixes to unbreak the docs buildbot. | George Burgess IV | 2016-06-21 | 1 | -1/+1 |
| | | | | | | | | | | | | | A number of warnings still remain, but these were the last of the "unlexable code"-related ones (AFAICT). I changed a few examples in docs/UsersManual.rst to showcase -Wextra-tokens because it's already documented (-Wmultichar isn't), and the sphinx C lexer apparently can't handle char literals like 'ab'. It seemed like a better overall approach than just marking the code blocks as none or console. llvm-svn: 273232 | ||||
* | [docs] Coverage: Document the profile merge pool specifier | Vedant Kumar | 2016-06-14 | 1 | -0/+8 |
| | | | | llvm-svn: 272604 | ||||
* | [docs] Coverage: Clarify return value of __llvm_profile_write_file | Vedant Kumar | 2016-06-08 | 1 | -2/+3 |
| | | | | llvm-svn: 272215 | ||||
* | [docs] Coverage: Flesh out instructions for avoiding static initializeres | Vedant Kumar | 2016-06-08 | 1 | -8/+16 |
| | | | | llvm-svn: 272214 | ||||
* | [docs] Coverage: Explain how to avoid static initializers | Vedant Kumar | 2016-06-07 | 1 | -0/+16 |
| | | | | llvm-svn: 272067 | ||||
* | [docs] Clarify limitations section of SourceBasedCodeCoverage.rst | Vedant Kumar | 2016-06-06 | 1 | -4/+5 |
| | | | | | | | | | Mention that the code coverage tool becomes less precise whenever unpredictable changes in control flow occur. Thanks to Sean Silva for pointing this out! llvm-svn: 271902 | ||||
* | [docs] Add a limitations section to SourceBasedCodeCoverage.rst | Vedant Kumar | 2016-06-02 | 1 | -2/+19 |
| | | | | llvm-svn: 271544 | ||||
* | [docs] Fix misplaced comma | Vedant Kumar | 2016-06-02 | 1 | -1/+1 |
| | | | | llvm-svn: 271472 | ||||
* | [docs] Minor formatting changes and typo fixes | Vedant Kumar | 2016-06-02 | 1 | -11/+10 |
| | | | | llvm-svn: 271471 | ||||
* | [docs] Use cpp code-blocks where appropriate | Vedant Kumar | 2016-06-02 | 1 | -2/+2 |
| | | | | llvm-svn: 271461 | ||||
* | [docs] Add missing newline to console section | Vedant Kumar | 2016-06-02 | 1 | -0/+1 |
| | | | | llvm-svn: 271457 | ||||
* | [docs] Document the source-based code coverage feature | Vedant Kumar | 2016-06-02 | 1 | -0/+186 |
Differential Revision: http://reviews.llvm.org/D20715 llvm-svn: 271454 |