maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
318,808 Commits 23 Branches 0 Tags 2.2 GiB
Commit Graph

6 Commits

Author SHA1 Message Date
Ying Yi 76eb219c9b [llvm-cov] Use the native path in the coverage report. 
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
 2016-08-30 07:01:37 +00:00
Vedant Kumar 71d515b0b3 [llvm-cov] Relax a test for Windows 
Attempt to address this bot failure:

  http://bb.pgr.jp/builders/ninja-clang-i686-msc19-R/builds/4967

llvm-svn: 275522
 2016-07-15 02:11:37 +00:00
Vedant Kumar b95dc4608d [llvm-cov] Improve error messages 
While we're at it, extend an existing test to make sure that error
messages look reasonable.

llvm-svn: 275520
 2016-07-15 01:53:39 +00:00
Vedant Kumar d6d192cd12 [llvm-cov] Use relative paths to file reports in -output-dir mode 
This makes it possible to e.g copy a report to another filesystem.

llvm-svn: 274173
 2016-06-29 21:55:46 +00:00
Vedant Kumar 2ca5eaa85a Fix a typo; NFC 
llvm-svn: 274136
 2016-06-29 16:23:34 +00:00
Vedant Kumar 4a54abeacd [llvm-cov] Do not allow ".." to escape the coverage sub-directory 
In -output-dir mode, file reports are placed into a "coverage"
directory. If filenames in the coverage mapping contain "..", they might
escape out of this directory.

Fix the problem by removing ".." from source filenames (expand the path
component).

llvm-svn: 274135
 2016-06-29 16:22:12 +00:00