search for: coveragereport

...eserve the old single-file behavior. We can add a release note about the new behavior. Great! I’d like to change the index.html page to only include coverage data for the filtered functions and do the same for all the ‘source view’ pages. For the index.html page I plan to do the filtering in `CoverageReport::prepareFileReports`, which will be quite simple. Filtering the lines in the source files will be more complicated, as I will need to find which function a LineSegment comes from. I think I can do that by getting the function coverage for each filtered function from the same file, and then check...

> On Sep 20, 2017, at 7:08 AM, Sean Eveson via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi All, > > > Normally when producing HTML with llvm-cov you get an index.html file and a directory structure containing .html files corresponding to source files. > > > Currently when using any of the -name*= command line options with -format=html, the output is

Hi All, Normally when producing HTML with llvm-cov you get an index.html file and a directory structure containing .html files corresponding to source files. Currently when using any of the -name*= command line options with -format=html, the output is a single file (functions.html) containing the coverage for those specific functions. Having a single file is not as useful as the full

...ld llvm[2]: Linking Release+Asserts executable llvm-dwarfdump (without symbols) llvm[2]: Compiling MachODumper.cpp for Release+Asserts build llvm[2]: Compiling CoverageFilters.cpp for Release+Asserts build llvm[2]: Linking Release+Asserts executable llvm-objdump (without symbols) llvm[2]: Compiling CoverageReport.cpp for Release+Asserts build llvm[2]: ======= Finished Linking Release+Asserts Executable llvm-dwarfdump (without symbols) make[2]: Leaving directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/tools/llvm-dwarfdump' llvm[2]: Compiling ObjDumper.cpp for Release+Asserts build llvm[2]: Compiling Coverag...