| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
llvm-svn: 281872
|
|
|
|
| |
llvm-svn: 281590
|
|
|
|
|
|
|
|
| |
Copying in the full text of the function doesn't help at all when we
already know that it's never executed. Just say that it's unexecuted --
the relevant source text has already been printed.
llvm-svn: 281589
|
|
|
|
|
|
|
| |
Doing so is pointless, since the whole view is usually visible in a
small amount of space.
llvm-svn: 281588
|
|
|
|
| |
llvm-svn: 281581
|
|
|
|
|
|
|
| |
Having the same title, timestamp, etc. occur repeatedly creates an
unnecessary distraction when paging through a report.
llvm-svn: 281579
|
|
|
|
|
|
|
| |
Having the version information in every view is distracting, especially
if there are several sub-views.
llvm-svn: 281414
|
|
|
|
|
|
|
|
|
|
| |
number>" in the coverage report.
The llvm-cov version information will be useful to the user when comparing the code coverage across different versions of llvm-cov. This patch provides the llvm-cov version information in the generated coverage report.
Differential Revision: https://reviews.llvm.org/D24457
llvm-svn: 281321
|
|
|
|
|
|
|
| |
Having it in the same row as the source name is jarring. Move it next to
the "Source" column label.
llvm-svn: 281146
|
|
|
|
|
|
|
| |
- Change the location of the 'Region Coverage' column.
- Use less css and text for some labels.
llvm-svn: 281145
|
|
|
|
|
|
|
|
|
|
|
| |
These asserts are making tests fragile. The renderer does not enter an
invalid state when they fail, however, it may spit out a garbled
coverage report because the source text no longer matches the provided
coverage mapping.
Another follow-up to r281072.
llvm-svn: 281076
|
|
|
|
|
|
|
|
|
|
| |
Treat filenames the same way in the text index as we do in the html
index. This is a follow-up to r281008 (an attempt to unbreak the
native_separators.c test on Windows).
Patch by Maggie Yi!
llvm-svn: 281062
|
|
|
|
|
|
|
|
| |
llvm-cov writes out an index file in '-output-dir' mode, albeit not a
very informative one. Try to fix that by using the CoverageReport API to
include some basic summary information in the index file.
llvm-svn: 281011
|
|
|
|
| |
llvm-svn: 281010
|
|
|
|
|
|
|
|
| |
It would be nice to prepare file reports (using the CoverageReport API)
without actually rendering them to the console. I plan on using this to
flesh out the 'index' files in the coverage views.
llvm-svn: 281009
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The text and html coverage views take different approaches to emitting
highlighted regions. That's because this problem is easier in the text
view: there's no need to worry about escaping text or adding tooltip
content to a highlighted snippet.
Unfortunately, the html view didn't get region highlighting quite right.
This patch fixes the situation, bringing parity between the two views.
llvm-svn: 280981
|
|
|
|
|
|
|
|
| |
In r279628, we made SourceCoverageView list the binary associated with a
view and started adding labels (e.g "Source: foo" or "Function: bar") to
everything. Condense this information a bit to unclutter reports.
llvm-svn: 280896
|
|
|
|
|
|
|
| |
Remove the longest common prefix from filenames when printing coverage
summaries. This makes them easier to compare.
llvm-svn: 280895
|
|
|
|
|
|
|
|
| |
Use the same color for counts and percentages. There doesn't seem to be
a reason for them to be different, and the summary looks more consistent
this way.
llvm-svn: 280765
|
|
|
|
| |
llvm-svn: 280764
|
|
|
|
|
|
|
|
|
|
| |
source file.
This patch is a spin-off from https://reviews.llvm.org/D23922. It extends the text view to preserve the same feature as the html view.
Differential Revision: https://reviews.llvm.org/D24241
llvm-svn: 280756
|
|
|
|
|
|
|
|
| |
This patch provides easy navigation to find the zero count lines, especially useful when the source file is very large.
Differential Revision: https://reviews.llvm.org/D23277
llvm-svn: 280739
|
|
|
|
| |
llvm-svn: 280181
|
|
|
|
|
|
|
|
|
|
|
| |
The coverage reports contain the source or binary file paths. On Windows,
the file path might contain the seperators of both '/' and '\'. This patch
uses the native path in the coverage reports. For example, on Windows,
all '/' are converted to '\'.
Differential Revision: https://reviews.llvm.org/D23922
llvm-svn: 280061
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch includes the following changes:
- Included header "Code coverage report" and include the date that the report was created.
- Included title (as specified in a command line option, (i.e llvm-cov -project-title="Simple Test")
- In the summary, list the elf files that the source code file has contributed to.
- Used column heading for "Line No.", "Count No.", Source".
Differential Revision: https://reviews.llvm.org/D23345
llvm-svn: 279628
|
|
|
|
|
|
|
|
|
| |
In the coverage report, the line and count columns have been swapped to make it more readable.
A follow-up commit in compiler-rt is needed
Differential Revision: https://reviews.llvm.org/D23281
llvm-svn: 278152
|
|
|
|
|
|
| |
Also, un-hide the cl::opt.
llvm-svn: 277741
|
|
|
|
|
|
|
|
|
|
|
| |
When using orbis-llvm-cov.exe to generate the HTML report, the HTML report
can look quite different to the source file if it includes tabs.The default
tab size is 2 spaces instead of 8 spaces. A command line switch is
be added to set the tab size.
Differential Revision: https://reviews.llvm.org/D23087
llvm-svn: 277715
|
|
|
|
|
|
|
| |
llvm-cov's `-dump' option now emits information which helps debug source
range highlighting in html mode.
llvm-svn: 276924
|
|
|
|
|
|
| |
This reverts commit r276906. It breaks tests.
llvm-svn: 276908
|
|
|
|
|
|
|
| |
This fixes the highlighting for lines without any coverage segments. I
don't have a neat way of testing this yet, but am working on it.
llvm-svn: 276906
|
|
|
|
|
|
|
| |
Test that Windows path separators are escaped properly. Add a round-trip
test to verify the JSON produced by the exporter.
llvm-svn: 276832
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This enables users to export coverage information as portable JSON for use by
analysis tools and storage in document based databases.
The export sub-command is invoked just like the others:
llvm-cov export -instr-profile path/to/foo.profdata path/to/foo.binary
The resulting JSON contains a list of files and functions. Every file object
contains a list of segments, expansions, and a summary of the file's region,
function, and line coverage. Every function object contains the function's name
and regions. There is also a total summary for the entire object file.
Changes since the initial commit (r276813):
- Fixed the regexes in the tests to handle Windows filepaths.
Patch by Eddie Hurtig!
Differential Revision: https://reviews.llvm.org/D22651
llvm-svn: 276818
|
|
|
|
|
|
|
|
|
| |
This reverts commit r276813. The Windows bots are complaining about some
of the filename regexes in the tests:
http://bb.pgr.jp/builders/ninja-clang-i686-msc19-R/builds/5299
llvm-svn: 276816
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This enables users to export coverage information as portable JSON for use by
analysis tools and storage in document based databases.
The export sub-command is invoked just like the others:
llvm-cov export -instr-profile path/to/foo.profdata path/to/foo.binary
The resulting JSON contains a list of files and functions. Every file object
contains a list of segments, expansions, and a summary of the file's region,
function, and line coverage. Every function object contains the function's name
and regions. There is also a total summary for the entire object file.
Patch by Eddie Hurtig!
Differential Revision: https://reviews.llvm.org/D22651
llvm-svn: 276813
|
|
|
|
|
|
| |
Just link in the stylesheet from the toplevel dir of the report.
llvm-svn: 276468
|
|
|
|
|
|
|
|
|
|
| |
The llvm-cov ‘report' command displays a summary of the coverage of a binary file.
The summary report currently only includes covered regions and covered functions.
This patch adds the coverage of lines in the summary report.
Differential Revision: https://reviews.llvm.org/D22569
llvm-svn: 276409
|
|
|
|
| |
llvm-svn: 276401
|
|
|
|
|
|
|
|
|
|
| |
This makes it easy to swap out the default stylesheet for a custom one.
It also shaves ~6.62 MB out of the report directory for a full coverage
build of llvm+clang.
While we're at it, prune the CSS and add tests for it.
llvm-svn: 276359
|
|
|
|
| |
llvm-svn: 275843
|
|
|
|
|
|
| |
Based on a suggestion by Harlan Haskins!
llvm-svn: 275840
|
|
|
|
|
|
| |
Use CodeCoverageTool::{error,warning} everywhere.
llvm-svn: 275837
|
|
|
|
|
|
|
|
|
|
| |
It's using a version of clang which can't (or won't) deduce an implicit
conversion from a SmallString to a StringRef. Write the conversion out
explicitly:
http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-buildserver/builds/8574
llvm-svn: 275647
|
|
|
|
|
|
|
|
|
| |
They appear to reject r275640 because stdin is held open during an
ExecuteAndWait in which it's redirected:
http://lab.llvm.org:8011/builders/llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast/builds/8390
llvm-svn: 275642
|
|
|
|
|
|
|
|
|
|
| |
Add an option to specify a symbol demangler (as well as options to the
demangler). This can be used to make reports more human-readable.
This option is especially useful in -output-dir mode, since it isn't as
easy to manually pipe reports into a demangler in this mode.
llvm-svn: 275640
|
|
|
|
| |
llvm-svn: 275639
|
|
|
|
|
|
|
| |
While we're at it, extend an existing test to make sure that error
messages look reasonable.
llvm-svn: 275520
|
|
|
|
|
|
|
|
|
|
|
| |
Taking a lock before appending to a vector does no good unless threads
reading from the vector also take the lock, because the vector could be
re-sized.
I don't have a good isolated test for this. I found the issue with ASan
while testing a large project. I'm working on a bot that does this.
llvm-svn: 275516
|
|
|
|
|
|
|
|
| |
Writing `for (StringRef &SourceFile : ...)` is strange to begin with.
Subsequently capturing "SourceFile" by reference is even stranger. Just
copy the StringRef, since that's cheap to do.
llvm-svn: 275515
|
|
|
|
| |
llvm-svn: 275514
|