1. 09 Jun, 2017 1 commit
  2. 08 Jun, 2017 1 commit
  3. 07 Jun, 2017 2 commits
  4. 29 May, 2017 1 commit
  5. 24 May, 2017 2 commits
  6. 09 May, 2017 6 commits
    • Michael Achenbach's avatar
      Reland "[test] Don't flatten testcfg globals" · d790a99d
      Michael Achenbach authored
      This reverts commit dd9dbf4d.
      
      Reason for revert: Fixed
      
      Bug: v8:6375
      Change-Id: Ied3fb991ba6f5774f5a2e6f13947b53f61196650
      Reviewed-on: https://chromium-review.googlesource.com/500133Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#45193}
      d790a99d
    • Michael Achenbach's avatar
      [test] Load the same suites in sub and parent test processes · dfddbd2d
      Michael Achenbach authored
      Before this fix, all existing suites would get wastefully initialized in each subprocess.
      
      Bug: v8:6375
      Change-Id: I68d961cde143754724735aecbac605852f89c7d9
      Reviewed-on: https://chromium-review.googlesource.com/500187Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#45188}
      dfddbd2d
    • Michael Achenbach's avatar
      Revert "Reland "[test] Don't flatten testcfg globals"" · dd9dbf4d
      Michael Achenbach authored
      This reverts commit 9a90717d.
      
      Reason for revert: Erroneous submit...
      
      Original change's description:
      > Reland "[test] Don't flatten testcfg globals"
      > 
      > This reverts commit 4fdf7cdf.
      > 
      > Reason for revert: Fixed
      > 
      > Original change's description:
      > > Revert "[test] Don't flatten testcfg globals"
      > > 
      > > This reverts commit 4fa473cb.
      > > 
      > > Reason for revert: Problems when v8 isn't located in a folder called "v8".
      > > 
      > > Original change's description:
      > > > [test] Don't flatten testcfg globals
      > > > 
      > > > This loads each test's testcfg.py as a unique module rather than flattening all into testcfg. Other than accessing LoadTestSuite there should be no references into testcfg files.
      > > > 
      > > > Bug: v8:6375
      > > > Change-Id: If863c1b35096b2589111e8091bb7d68f135da674
      > > > Reviewed-on: https://chromium-review.googlesource.com/498807
      > > > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org>
      > > > Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      > > > Cr-Commit-Position: refs/heads/master@{#45178}
      > > 
      > > TBR=jkummerow@chromium.org,machenbach@chromium.org
      > > NOPRESUBMIT=true
      > > NOTREECHECKS=true
      > > NOTRY=true
      > > Bug: v8:6375
      > > 
      > > Change-Id: I3600b54279c0d98a39475432c5b2163f510153f0
      > > Reviewed-on: https://chromium-review.googlesource.com/500130
      > > Reviewed-by: Michael Achenbach <machenbach@chromium.org>
      > > Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      > > Cr-Commit-Position: refs/heads/master@{#45180}
      > 
      > TBR=jkummerow@chromium.org,machenbach@chromium.org,v8-reviews@googlegroups.com
      > NOPRESUBMIT=true
      > NOTREECHECKS=true
      > NOTRY=true
      > Bug: v8:6375
      > 
      > Change-Id: I8198b74ff8e1c3aa179769bef24f204dc705da67
      > Reviewed-on: https://chromium-review.googlesource.com/500131
      > Reviewed-by: Michael Achenbach <machenbach@chromium.org>
      > Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#45181}
      
      TBR=jkummerow@chromium.org,machenbach@chromium.org,v8-reviews@googlegroups.com
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      Bug: v8:6375
      
      Change-Id: Id8ab1c3482806b613a024d4fff5c84a7ab0d2b0b
      Reviewed-on: https://chromium-review.googlesource.com/500132Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#45182}
      dd9dbf4d
    • Michael Achenbach's avatar
      Reland "[test] Don't flatten testcfg globals" · 9a90717d
      Michael Achenbach authored
      This reverts commit 4fdf7cdf.
      
      Reason for revert: Fixed
      
      Original change's description:
      > Revert "[test] Don't flatten testcfg globals"
      > 
      > This reverts commit 4fa473cb.
      > 
      > Reason for revert: Problems when v8 isn't located in a folder called "v8".
      > 
      > Original change's description:
      > > [test] Don't flatten testcfg globals
      > > 
      > > This loads each test's testcfg.py as a unique module rather than flattening all into testcfg. Other than accessing LoadTestSuite there should be no references into testcfg files.
      > > 
      > > Bug: v8:6375
      > > Change-Id: If863c1b35096b2589111e8091bb7d68f135da674
      > > Reviewed-on: https://chromium-review.googlesource.com/498807
      > > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org>
      > > Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      > > Cr-Commit-Position: refs/heads/master@{#45178}
      > 
      > TBR=jkummerow@chromium.org,machenbach@chromium.org
      > NOPRESUBMIT=true
      > NOTREECHECKS=true
      > NOTRY=true
      > Bug: v8:6375
      > 
      > Change-Id: I3600b54279c0d98a39475432c5b2163f510153f0
      > Reviewed-on: https://chromium-review.googlesource.com/500130
      > Reviewed-by: Michael Achenbach <machenbach@chromium.org>
      > Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#45180}
      
      TBR=jkummerow@chromium.org,machenbach@chromium.org,v8-reviews@googlegroups.com
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      Bug: v8:6375
      
      Change-Id: I8198b74ff8e1c3aa179769bef24f204dc705da67
      Reviewed-on: https://chromium-review.googlesource.com/500131Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#45181}
      9a90717d
    • Michael Achenbach's avatar
      Revert "[test] Don't flatten testcfg globals" · 4fdf7cdf
      Michael Achenbach authored
      This reverts commit 4fa473cb.
      
      Reason for revert: Problems when v8 isn't located in a folder called "v8".
      
      Original change's description:
      > [test] Don't flatten testcfg globals
      > 
      > This loads each test's testcfg.py as a unique module rather than flattening all into testcfg. Other than accessing LoadTestSuite there should be no references into testcfg files.
      > 
      > Bug: v8:6375
      > Change-Id: If863c1b35096b2589111e8091bb7d68f135da674
      > Reviewed-on: https://chromium-review.googlesource.com/498807
      > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org>
      > Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#45178}
      
      TBR=jkummerow@chromium.org,machenbach@chromium.org
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      Bug: v8:6375
      
      Change-Id: I3600b54279c0d98a39475432c5b2163f510153f0
      Reviewed-on: https://chromium-review.googlesource.com/500130Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#45180}
      4fdf7cdf
    • Michael Achenbach's avatar
      [test] Don't flatten testcfg globals · 4fa473cb
      Michael Achenbach authored
      This loads each test's testcfg.py as a unique module rather than flattening all into testcfg. Other than accessing LoadTestSuite there should be no references into testcfg files.
      
      Bug: v8:6375
      Change-Id: If863c1b35096b2589111e8091bb7d68f135da674
      Reviewed-on: https://chromium-review.googlesource.com/498807Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#45178}
      4fa473cb
  7. 04 May, 2017 1 commit
  8. 28 Apr, 2017 1 commit
  9. 11 Apr, 2017 3 commits
  10. 29 Mar, 2017 1 commit
  11. 27 Mar, 2017 1 commit
  12. 24 Mar, 2017 3 commits
  13. 23 Mar, 2017 1 commit
  14. 14 Mar, 2017 2 commits
  15. 13 Mar, 2017 4 commits
  16. 10 Mar, 2017 1 commit
  17. 09 Mar, 2017 1 commit
  18. 02 Mar, 2017 1 commit
  19. 01 Mar, 2017 2 commits
    • bmeurer's avatar
      Revert of [wasm] Initial signal handler (patchset #56 id:1090001 of... · 0b3e554e
      bmeurer authored
      Revert of [wasm] Initial signal handler (patchset #56 id:1090001 of https://codereview.chromium.org/2371833007/ )
      
      Reason for revert:
      Breaks tree, i.e. https://build.chromium.org/p/client.v8/builders/V8%20Linux64%20ASAN/builds/18928/steps/Check/logs/grow-memory
      
      Original issue's description:
      > [wasm] Initial signal handler
      >
      > This is basically the minimum viable signal handler for Wasm bounds checks.
      > It includes the TLS check and the fine grained instructions checks. These
      > two checks provide most of the safety for the signal handler. Future CLs will
      > add code range and data range checks for more robustness.
      >
      > The trap handling code and data structures are all in src/trap-handler, with
      > the code that actually runs in the signal handler confined to
      > src/trap-handler/signal-handler.cc.
      >
      > This changes adds a new V8 API that the embedder should call from a signal
      > handler that will give V8 the chance to handle the fault first. For hosts that
      > do not want to implement their own signal handler, we include the option to
      > install a simple one. This simple handler is also used for the tests.
      >
      > When a Wasm module is instantiated, information about each function is passed
      > to the trap handler, which is used to classify faults. These are removed during
      > the instance finalizer.
      >
      > Several future enhancements are planned before turning this on by default.
      > Obviously, the additional checks will be added to MaybeHandleFault. We are
      > also planning to add a two-level CodeObjectData table that is grouped by
      > isolates to make cleanup easier and also reduce potential for contending on
      > a single data structure.
      >
      > BUG= https://bugs.chromium.org/p/v8/issues/detail?id=5277
      >
      > Review-Url: https://codereview.chromium.org/2371833007
      > Cr-Commit-Position: refs/heads/master@{#43523}
      > Committed: https://chromium.googlesource.com/v8/v8/+/a5af7fe9ee388a636675f4a6872b1d34fa7d1a7a
      
      TBR=ahaas@chromium.org,bradnelson@google.com,hpayer@chromium.org,jochen@chromium.org,mark@chromium.org,mseaborn@chromium.org,titzer@chromium.org,eholk@chromium.org
      # Skipping CQ checks because original CL landed less than 1 days ago.
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      BUG= https://bugs.chromium.org/p/v8/issues/detail?id=5277
      
      Review-Url: https://codereview.chromium.org/2723133003
      Cr-Commit-Position: refs/heads/master@{#43525}
      0b3e554e
    • eholk's avatar
      [wasm] Initial signal handler · a5af7fe9
      eholk authored
      This is basically the minimum viable signal handler for Wasm bounds checks.
      It includes the TLS check and the fine grained instructions checks. These
      two checks provide most of the safety for the signal handler. Future CLs will
      add code range and data range checks for more robustness.
      
      The trap handling code and data structures are all in src/trap-handler, with
      the code that actually runs in the signal handler confined to
      src/trap-handler/signal-handler.cc.
      
      This changes adds a new V8 API that the embedder should call from a signal
      handler that will give V8 the chance to handle the fault first. For hosts that
      do not want to implement their own signal handler, we include the option to
      install a simple one. This simple handler is also used for the tests.
      
      When a Wasm module is instantiated, information about each function is passed
      to the trap handler, which is used to classify faults. These are removed during
      the instance finalizer.
      
      Several future enhancements are planned before turning this on by default.
      Obviously, the additional checks will be added to MaybeHandleFault. We are
      also planning to add a two-level CodeObjectData table that is grouped by
      isolates to make cleanup easier and also reduce potential for contending on
      a single data structure.
      
      BUG= https://bugs.chromium.org/p/v8/issues/detail?id=5277
      
      Review-Url: https://codereview.chromium.org/2371833007
      Cr-Commit-Position: refs/heads/master@{#43523}
      a5af7fe9
  20. 13 Feb, 2017 1 commit
  21. 09 Feb, 2017 1 commit
  22. 07 Feb, 2017 1 commit
  23. 06 Jan, 2017 1 commit
  24. 18 Nov, 2016 1 commit
    • marja's avatar
      Remove FLAG_min_preparse_length. · 4a5b7e32
      marja authored
      It originates from the era where we used to run a separate preparse step
      before parsing and store the function data. Now the usage of preparser
      is something completely different, so this flag doesn't make sense any
      more.
      
      In addition, this way we get more test coverage for preparser (for small
      scripts).
      
      BUG=
      
      Review-Url: https://codereview.chromium.org/2513563002
      Cr-Commit-Position: refs/heads/master@{#41110}
      4a5b7e32