1. 19 Jan, 2017 37 commits
  2. 18 Jan, 2017 3 commits
    • kozyatinskiy's avatar
      [inspector] introduced debug::SetBreakEventListener,SetExceptionEventListener · f3dcdf88
      kozyatinskiy authored
      Inspector is moved to per-event-type callbacks instead of general v8::debug::SetDebugEventListener. It allows to:
      - remove any usage of v8::Debug::EventDetails in debug-interface,
      - avoid redundant JS call on each event to get properties of event objects,
      - introduce better pure C++ API for these events later.
      
      BUG=v8:5510
      R=yangguo@chromium.org,jgruber@chromium.org,dgozman@chromium.org
      
      Review-Url: https://codereview.chromium.org/2622253004
      Cr-Commit-Position: refs/heads/master@{#42483}
      f3dcdf88
    • bjaideep's avatar
      PPC/s390: [Turbofan] Implement super calls with spread bytecode in assembly code. · ea4f834c
      bjaideep authored
      Port 0b8200c7
      
      R=petermarshall@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
      BUG=v8:5659
      LOG=N
      
      Review-Url: https://codereview.chromium.org/2645683002
      Cr-Commit-Position: refs/heads/master@{#42482}
      ea4f834c
    • binji's avatar
      Implement ldrex/strex instructions in ARM simulator · 66ae5f7d
      binji authored
      This CL implements ldrex, ldrexb, ldrexh, strex, strexb, and strexh in the
      Simulator. These instructions provide "exclusive" access, which provides mutual
      exclusion for concurrent threads of execution.
      
      The ARM specification gives some leeway to implementors, but essentially
      describes each processor as having Local Monitor and Global Monitor. The Local
      Monitor is used to check the exclusivity state without having to synchronize
      with other processors. The Global Monitor is shared between processors. We
      model both to make it easier to match behavior with the spec.
      
      When running with multiple OS threads, each thread has its own isolate, and
      each isolate has its own Simulator. The Local Monitor is stored directly on the
      Simulator, and the Global Monitor is stored as a lazy singleton. The Global
      Monitor maintains a linked-list of all Simulators.
      
      All loads/stores (even non-exclusive) are guarded by the Global Monitor's mutex.
      
      BUG=v8:4614
      
      Review-Url: https://codereview.chromium.org/2006183004
      Cr-Commit-Position: refs/heads/master@{#42481}
      66ae5f7d