Displaying 3 results from an estimated 3 matches for "linesegment".
2017 Sep 21
1
[llvm-cov] Single file HTML output when filtering on function names.
...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 checking if the line segment can be found in any of those. I
was wondering if you can think of a better way of mapping from lines to
functions or if you might have something el...
2017 Sep 20
0
[llvm-cov] Single file HTML output when filtering on function names.
> 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
2017 Sep 20
2
[llvm-cov] Single file HTML output when filtering on function names.
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