1. 14 Apr, 2016 2 commits
  2. 13 Apr, 2016 2 commits
  3. 08 Apr, 2016 1 commit
  4. 03 Apr, 2016 1 commit
  5. 31 Mar, 2016 1 commit
  6. 24 Mar, 2016 2 commits
  7. 22 Mar, 2016 1 commit
  8. 21 Mar, 2016 1 commit
  9. 10 Mar, 2016 1 commit
  10. 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
  11. 25 Feb, 2016 4 commits
  12. 24 Feb, 2016 3 commits
  13. 23 Feb, 2016 1 commit
  14. 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
  15. 18 Feb, 2016 2 commits
  16. 17 Feb, 2016 1 commit
  17. 15 Feb, 2016 2 commits
  18. 08 Feb, 2016 1 commit
  19. 04 Feb, 2016 1 commit
  20. 27 Jan, 2016 1 commit
    • brucedawson's avatar
      Get v8 builds to use up-to-date VS toolchains · aa354d3f
      brucedawson authored
      The VS 2013 toolchain used by v8 is ~two months out of date. The
      Chromium toolchain was updated in October to include the Windows 10
      SDK. Using a different toolchain in v8 leads to the possibility of
      odd incompatibilities, and means that switching between Chromium and
      v8 requires a time-consuming reinstallation of the toolchain. The
      VS 2013 toolchain was updated by crrev.com/1502563003.
      
      The VS 2015 toolchain used by v8 is also out of date. It is the wrong
      compiler version (RTM instead of Update 1), the wrong SDK version, and
      it is missing files such as the UCRT installers.
      
      LOG=N
      BUG=440500,491424
      
      Review URL: https://codereview.chromium.org/1632363002
      
      Cr-Commit-Position: refs/heads/master@{#33560}
      aa354d3f
  21. 26 Jan, 2016 1 commit
  22. 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
  23. 08 Jan, 2016 2 commits
  24. 05 Jan, 2016 1 commit
  25. 04 Jan, 2016 1 commit
    • machenbach's avatar
      [test] Add ignition test set. · ee665067
      machenbach authored
      Add control for the ignition test suites. This will be
      followed by a change on the infra side that targets the
      ignition set instead of the hardcoded mjsunit.
      
      After that, cctest can be enabled in a separate CL. This CL
      already includes the logic for running cctest for ignition
      on swarming.
      
      BUG=v8:4280
      LOG=N
      
      Review URL: https://codereview.chromium.org/1559943002
      
      Cr-Commit-Position: refs/heads/master@{#33089}
      ee665067
  26. 24 Dec, 2015 1 commit
  27. 18 Dec, 2015 1 commit
  28. 17 Dec, 2015 2 commits