1. 25 Jul, 2018 6 commits
  2. 24 Jul, 2018 7 commits
  3. 23 Jul, 2018 1 commit
  4. 20 Jul, 2018 4 commits
    • Sigurd Schneider's avatar
      Speculatively revert "[turboassembler] Introduce hard-abort mode" · 039c18e1
      Sigurd Schneider authored
      This reverts commit a462a785.
      
      Reason for revert: Breaks a TurboAssembler test:
      https://ci.chromium.org/p/v8/builders/luci.v8.ci/V8%20Arm/7726
      
      Original change's description:
      > [turboassembler] Introduce hard-abort mode
      > 
      > For checks and assertions (mostly for debug code, like stack alignment
      > or zero extension), we had two modes: Emit a call to the {Abort}
      > runtime function (the default), and emit a debug break (used for
      > testing, enabled via --trap-on-abort).
      > In wasm, where we cannot just call a runtime function because code must
      > be isolate independent, we always used the trap-on-abort behaviour.
      > This causes problems for our fuzzers, which do not catch SIGTRAP, and
      > hence do not detect debug code failures.
      > 
      > This CL introduces a third mode ("hard abort"), which calls a C
      > function via {ExternalReference}. The C function still outputs the
      > abort reason, but does not print the stack trace. It then aborts via
      > "OS::Abort", just like the runtime function.
      > This will allow fuzzers to detect the crash and even find a nice error
      > message.
      > 
      > Even though this looks like a lot of code churn, it is actually not.
      > Most added lines are new tests, and other changes are minimal.
      > 
      > R=​mstarzinger@chromium.org
      > 
      > Bug: chromium:863799
      > Change-Id: I77c58ff72db552d49014614436259ccfb49ba87b
      > Reviewed-on: https://chromium-review.googlesource.com/1142163
      > Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#54592}
      
      TBR=mstarzinger@chromium.org,clemensh@chromium.org
      
      Change-Id: I60c011cfe262ccebbb9abf32699a9fe17e72a3c8
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: chromium:863799
      Reviewed-on: https://chromium-review.googlesource.com/1145431
      Commit-Queue: Sigurd Schneider <sigurds@chromium.org>
      Reviewed-by: 's avatarSigurd Schneider <sigurds@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#54597}
      039c18e1
    • Clemens Hammacher's avatar
      [turboassembler] Introduce hard-abort mode · a462a785
      Clemens Hammacher authored
      For checks and assertions (mostly for debug code, like stack alignment
      or zero extension), we had two modes: Emit a call to the {Abort}
      runtime function (the default), and emit a debug break (used for
      testing, enabled via --trap-on-abort).
      In wasm, where we cannot just call a runtime function because code must
      be isolate independent, we always used the trap-on-abort behaviour.
      This causes problems for our fuzzers, which do not catch SIGTRAP, and
      hence do not detect debug code failures.
      
      This CL introduces a third mode ("hard abort"), which calls a C
      function via {ExternalReference}. The C function still outputs the
      abort reason, but does not print the stack trace. It then aborts via
      "OS::Abort", just like the runtime function.
      This will allow fuzzers to detect the crash and even find a nice error
      message.
      
      Even though this looks like a lot of code churn, it is actually not.
      Most added lines are new tests, and other changes are minimal.
      
      R=mstarzinger@chromium.org
      
      Bug: chromium:863799
      Change-Id: I77c58ff72db552d49014614436259ccfb49ba87b
      Reviewed-on: https://chromium-review.googlesource.com/1142163
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#54592}
      a462a785
    • Clemens Hammacher's avatar
      [iwyu] Add script to check that headers can be included in isolation · 4b412577
      Clemens Hammacher authored
      The most important point of IWYU (include-what-you-use) is that each
      header includes everything it is using, so that whoever includes that
      header does not need to additionally include other things.
      This CL adds a script which generates files to automatically check this.
      It is automatically invoked during "gclient runhooks" if the
      "check_v8_header_includes" variable is set. This script generates a
      number of .cc files in the "check-header-includes" directory, together
      with a "sources.gni" file which lists all the generated cc files. Each
      file includes one header.
      If additionally the gn args "v8_check_header_includes" is set, this gni
      file is included, and all the generated CC files will be compiled. This
      will detect violations of the aforementioned IWYU rule.
      
      R=titzer@chromium.org, machenbach@chromium.org
      
      Bug: v8:7754, v8:7965
      Change-Id: Id1cf256507052c3a9ea82f8c80ea1c0385457e31
      Reviewed-on: https://chromium-review.googlesource.com/1145199
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Reviewed-by: 's avatarBen Titzer <titzer@chromium.org>
      Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#54590}
      4b412577
    • Yang Guo's avatar
      [tools] opt out of metrics when fetching deps for node · 2ebce7a8
      Yang Guo authored
      R=machenbach@chromium.org
      
      Change-Id: Ia50f6e637aec58e9c1bdd726c84b296fd71d7cbb
      Reviewed-on: https://chromium-review.googlesource.com/1142767Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Yang Guo <yangguo@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#54571}
      2ebce7a8
  5. 19 Jul, 2018 3 commits
  6. 18 Jul, 2018 3 commits
  7. 17 Jul, 2018 1 commit
  8. 16 Jul, 2018 3 commits
  9. 13 Jul, 2018 2 commits
  10. 12 Jul, 2018 1 commit
  11. 11 Jul, 2018 3 commits
  12. 10 Jul, 2018 3 commits
  13. 09 Jul, 2018 3 commits
    • Sigurd Schneider's avatar
      [tools] Add an averaging script · 95ab7579
      Sigurd Schneider authored
      This script averages numbers output from another script. It is useful
      to average over a benchmark that outputs one or more results of the form
        <key> <number> <unit>
      key and unit are optional.
      
      For example, if
        $ bch --allow-natives-syntax toNumber.js
      outputs
        Number('undefined'):  155763 Kps
        (+'undefined'):  193050 Kps
        parseFloat('undefined'):  23736 Kps
      then
        $ avg.py 10 bch --allow-natives-syntax toNumber.js
      will output
        [10/10] (+'undefined')         : avg 192,240.40 stddev   6,486.24 (185,529.00 - 206,186.00) Kps
        [10/10] Number('undefined')    : avg 156,990.10 stddev  16,327.56 (144,718.00 - 202,840.00) Kps
        [10/10] parseFloat('undefined'): avg  22,885.80 stddev   1,941.80 ( 17,584.00 -  24,266.00) Kps
      
      Change-Id: I237706da8ade1b152e04084e0189007460d359c5
      Reviewed-on: https://chromium-review.googlesource.com/1128747
      Commit-Queue: Sigurd Schneider <sigurds@chromium.org>
      Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#54330}
      95ab7579
    • Clemens Hammacher's avatar
      Fix and extend lldbinit · 5b744bfb
      Clemens Hammacher authored
      1) Define all commands in one file.
      2) Add logic to make 'jco' print current pc by default.
      3) Add a comment to explain how to load the lldb_commands.py file.
      4) Minor refactorings.
      
      R=ahaas@chromium.org
      No-Try: true
      
      Bug: v8:7754
      Change-Id: I553f2ce4cefedad05466c692a8665a570372b76a
      Reviewed-on: https://chromium-review.googlesource.com/1127892Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#54329}
      5b744bfb
    • Leszek Swirski's avatar
      [sfi] Replace start/end position with UncompiledData · 39e2d97b
      Leszek Swirski authored
      Add new types for function data for SharedFunctionInfo, for uncompiled
      functions. UncompiledData holds start/end positions, allowing us to
      remove these fields from SFI. Uncompiled functions with pre-parsed
      scope data now hold an UncompiledDataWithScope that has a pointer to
      PreParsedScopeData -- this allows us to also remove the start/end pos
      from PreParsedScopeData.
      
      Bug: chromium:818642
      Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng
      Change-Id: I56f3c4e62cbf38929babac734a332709f12a8202
      Reviewed-on: https://chromium-review.googlesource.com/1126381
      Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
      Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarToon Verwaest <verwaest@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Reviewed-by: 's avatarMarja Hölttä <marja@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#54319}
      39e2d97b