Skip to content

V
V8
Switch branch/tag
  1. 20 Apr, 2016 1 commit
  3. 18 Apr, 2016 2 commits
  5. 15 Apr, 2016 1 commit
  7. 14 Apr, 2016 3 commits
  9. 13 Apr, 2016 1 commit
  11. 08 Apr, 2016 1 commit
  13. 31 Mar, 2016 1 commit
  15. 24 Mar, 2016 2 commits
  17. 22 Mar, 2016 1 commit
  19. 08 Mar, 2016 1 commit
    • machenbach's avatar
      [coverage] Enable sanitizer coverage. · 33ffced5
      machenbach authored 
      This adds sanitizer-coverage compilation, test-runner
features and post processing.

Sanitizer coverage is expected to be used together with
asan.

During test runner execution, the produced sancov files
are disambiguated and match the pattern:
<executable name>.test.<test id>.sancov.

Two additional scripts are added for merging raw sancov
files and for generating json data containing all
instrumented lines + all covered lines from merged sancov
files. Both scripts use multiprocessing for speed.

The json data will later be uploaded to google storage
for further use, e.g. to show coverage data in rietveld.

Sancov documentation:
http://clang.llvm.org/docs/SanitizerCoverage.html

BUG=chromium:568949
LOG=n
NOTRY=true
TEST=python -m unittest sancov_formatter_test
TEST=python -m unittest sancov_merger_test

Review URL: https://codereview.chromium.org/1737263003

Cr-Commit-Position: refs/heads/master@{#34578}
      33ffced5
  21. 25 Feb, 2016 4 commits
  23. 24 Feb, 2016 3 commits
  25. 23 Feb, 2016 1 commit
  27. 22 Feb, 2016 1 commit
    • machenbach's avatar
      [coverage] Use optimized builds for coverage data. · ea0530af
      machenbach authored 
      Local testing suggests that optimized builds add more speed
without trading off tool usability. We get the following
differences (A: non-optimized build, B: optimized):

Sometimes: Lines instrumented in A (covered and uncovered) are not instrumented in B.
Rarely: Lines instrumented and covered in A are instrumented, but not covered in B.

The latter might simply be caused by timing differences in
the two builds.

BUG=chromium:568949
LOG=n
NOTRY=true

Review URL: https://codereview.chromium.org/1719923002

Cr-Commit-Position: refs/heads/master@{#34193}
      ea0530af
  29. 17 Feb, 2016 1 commit
  31. 15 Feb, 2016 1 commit
  33. 08 Feb, 2016 1 commit
  35. 04 Feb, 2016 1 commit
  37. 14 Jan, 2016 1 commit
    • joransiu's avatar
      S390: Makefile + Build Toolchain Updates · 1091c2f0
      joransiu authored 
      This is the first of several commits to contribute Linux on z Systems
(s390/s390x) port of V8.  We will be breaking up the changes into several
(hopefully) logical commits.

This commit contains the changes to V8 Makefile and build toolchains to
introduce S390 macros and compiler options.  Just for awareness for reviewers
is that s390 is 31-bit (not 32!) big-endian platform on Linux on z.  (MSB of address
is used to distinguish between 24-bit vs 31-bit addressing!)  s390x is
64-bit Linux on z.  Names follow the general linux convention on the platform.

A quick roadmap on upcoming commits:
- Add \#include of S390 header files in common files
- S390 related tests + tooling changes
- printf macro for printing size_t values.
- S390 platform-specific code generation code (bulk of changes!)

R=danno@chromium.org,svenpanne@chromium.org,michael_dawson@ca.ibm.com,jyan@ca.ibm.com,mtbrandyberry@ca.ibm.com
BUG=

Review URL: https://codereview.chromium.org/1585813002

Cr-Commit-Position: refs/heads/master@{#33304}
      1091c2f0
  39. 08 Jan, 2016 1 commit
  41. 24 Dec, 2015 1 commit
  43. 17 Dec, 2015 1 commit
  45. 10 Dec, 2015 1 commit
  47. 09 Dec, 2015 1 commit
  49. 02 Dec, 2015 1 commit
  51. 27 Nov, 2015 1 commit
  53. 26 Nov, 2015 1 commit
  55. 24 Nov, 2015 1 commit
  57. 20 Nov, 2015 1 commit
  59. 04 Nov, 2015 1 commit
  61. 02 Nov, 2015 1 commit