1. 16 Nov, 2016 5 commits
    • jing.bao's avatar
      X87: Add chunyang.dai@intel.com to X87 folder OWNER file · 5716db5d
      jing.bao authored
      BUG=
      
      Review-Url: https://codereview.chromium.org/2509603002
      Cr-Commit-Position: refs/heads/master@{#41020}
      5716db5d
    • jgruber's avatar
      [debug-wrapper] Further extend the debug wrapper · b06c4ce5
      jgruber authored
      This CL further extends the debug wrapper, migrates around 60 tests, and
      removes a few tests that use functionality we will not support anymore.
      
      In more detail:
      
      * Removed tests that use:
        * enable/disable individual breakpoints
        * invocationText()
        * the ScriptCollected event
        * showBreakPoints
        * evalFromScript (and similar)
        * mirror.constructedBy and mirror.referencedBy
        * event_data.promise()
      * Some frame.evaluate uses were adapted since due to differences between
        remote objects (inspector) and mirrors. For instance, exceptions are
        currently not recreated exactly, since the inspector protocol does not
        give us the stack and message separately. Other objects (such as
        'this' in debug-evaluate-receiver-before-super) need to be explicitly
        converted to a string before the test works correctly.
      * Ensure that inspector stores the script before sending ScriptParsed and
        ScriptFailedToParse events in order to be able to use the script from
        within those events.
      * Better remote object reconstruction (e.g. for undefined and arrays).
      * New functionality in wrapper:
        * debuggerFlags().breakPointsActive.setValue()
        * scripts()
        * execState.setVariableValue()
        * execState.scopeObject().value()
        * execState.scopeObject().property()
        * execState.frame().allScopes()
        * eventData.exception()
        * eventData.script()
        * setBreakPointsActive()
      
      BUG=v8:5530
      
      Review-Url: https://codereview.chromium.org/2497973002
      Cr-Commit-Position: refs/heads/master@{#41019}
      b06c4ce5
    • machenbach's avatar
      Revert of [refactoring] Split CodeAssemblerState out of CodeAssembler... · 41a06267
      machenbach authored
      Revert of [refactoring] Split CodeAssemblerState out of CodeAssembler (patchset #8 id:140001 of https://codereview.chromium.org/2498073002/ )
      
      Reason for revert:
      https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20shared doesn't want to compile. Missing export annotation?
      
      Original issue's description:
      > [refactoring] Split CodeAssemblerState out of CodeAssembler
      >
      > This is in preparation for introducing more specialized
      > CodeStubAssembler subclasses. The state object can be handed
      > around, while the Assembler instances are temporary-scoped.
      >
      > BUG=v8:5628
      
      TBR=ishell@chromium.org,mstarzinger@chromium.org,jkummerow@chromium.org
      # Skipping CQ checks because original CL landed less than 1 days ago.
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      BUG=v8:5628
      
      Review-Url: https://codereview.chromium.org/2504913002
      Cr-Commit-Position: refs/heads/master@{#41018}
      41a06267
    • bmeurer's avatar
      [turbofan] Specialize to (optimization time) known TypedArray instances. · 4db73ae0
      bmeurer authored
      When we have a known JSTypedArray instance at optimization time, i.e. as
      in asm.js-like use cases and also when there are global typed arrays that
      are tracked via global object property constant tracking, we can generate
      more efficient code in that case by specializing to the immutable internal
      fields of the JSTypedArray (and the JSArrayBuffer backing it).
      
      R=jarin@chromium.org
      BUG=v8:4470,v8:5267
      
      Review-Url: https://codereview.chromium.org/2510553002
      Cr-Commit-Position: refs/heads/master@{#41017}
      4db73ae0
    • bmeurer's avatar
      [turbofan][x64] Try harder to use memory addressing modes. · f16a7fe3
      bmeurer authored
      When we don't have a base, and the displacement returned by the
      BaseWithIndexAndDisplacement64Matcher cannot be encoded as immediate,
      we can still try to utilize the scale factor matching by just using
      the displacement as base. This happens when we do indexed memory
      accesses to known addresses.
      
      R=jarin@chromium.org
      
      Review-Url: https://codereview.chromium.org/2504123002
      Cr-Commit-Position: refs/heads/master@{#41016}
      f16a7fe3
  2. 15 Nov, 2016 35 commits