summaryrefslogtreecommitdiffstats
path: root/llvm/utils/prepare-code-coverage-artifact.py
Commit message (Collapse)AuthorAgeFilesLines
* [utils] coverage: Add help text about the --restrict flag (NFC)Vedant Kumar2017-02-091-1/+5
| | | | | | | | | | Passing the --restrict flag to the coverage prep script before other positional arguments is wrong, because it prevents the argparse module from telling apart arguments to --restrict versus positional arguments. Pointed out by Sean Callanan! llvm-svn: 294616
* [utils] Add a '--unified-report' option to the code coverage prep scriptVedant Kumar2016-10-261-12/+29
| | | | | | | | | | | In --unified-report mode, a single coverage report is prepared for all specified binaries and written to *report_dir*. This mode is compatible with all existing script options, including the --restrict mode which is used to limit coverage reporting to certain files or directories. This should not break any existing users of the script. llvm-svn: 285249
* [utils] Use print_function in the code coverage prep script, NFC.Vedant Kumar2016-10-261-5/+7
| | | | llvm-svn: 285248
* [utils] Add an '--only-merge' option to the code coverage prep scriptVedant Kumar2016-10-261-3/+11
| | | | | | | | | | | In --only-merge mode, the script terminates after the profile merging step. This makes the script less stateful: it's more natural to split the merge out into a separate step instead of relying on the first invocation of the script to do it. This should not break any existing users of the script. llvm-svn: 285247
* [utils] Teach the code coverage prep script about --restrictVedant Kumar2016-09-221-14/+27
| | | | | | | | | | | | | | Add two options to the code coverage artifact prep script: * --use-existing-profdata: Use an existing indexed profile instead of merging the same profiles again. * --restrict: Restrict the coverage reporting to the given list of source directories. With this in place, we can teach the coverage bot how to prepare separate reports for each of the llvm tools. llvm-svn: 282204
* [utils] Generate html reports with the code coverage utility scriptVedant Kumar2016-07-181-19/+31
| | | | | | | | | | | Instead of extracting raw coverage mappings into an artifact directory, actually generate useful html reports for a given list of binaries with symbol demangling turned on. No tests, but this is actively being used to drive the (still nascent) coverage bot. llvm-svn: 275927
* Add support for collating profiles for use with code coverageVedant Kumar2016-06-131-0/+55
Differential Revision: http://reviews.llvm.org/D20993 llvm-svn: 272599
OpenPOWER on IntegriCloud