1. 21 Sep, 2015 5 commits
    • mythria's avatar
      Continuing removing deprecated function from cctest · 41111e3d
      mythria authored
      Removes deprecated functions from the following files:
      
      test/cctest/compiler/function-tester.h
      test/cctest/test-thread-termination.cc
      test/cctest/test-threads.cc
      test/cctest/test-transitions.cc
      test/cctest/test-typedarrays.cc
      test/cctest/test-types.cc
      test/cctest/test-typing-reset.cc
      test/cctest/test-unbound-queue.cc
      test/cctest/test-unboxed-doubles.cc
      
      BUG=v8:4134
      LOG=n
      
      Review URL: https://codereview.chromium.org/1344583002
      
      Cr-Commit-Position: refs/heads/master@{#30846}
      41111e3d
    • chunyang.dai's avatar
      X87: [stubs] Refactor StringCompareStub and use it for HStringCompareAndBranch. · be04dd5c
      chunyang.dai authored
      port 8016547c (r30818).
      
      original commit message:
      
          The StringCompareStub used to take its parameters on the (JavaScript)
          stack, which made it impossible to use in TurboFan. Actually
          StringCompareStub was currently completely unused. This changes the
          calling convention to something TurboFan compatible and introduces a
          CallInterfaceDescriptor for StringCompareStub. It also changes
          HStringCompareAndBranch to use the StringCompareStub instead of using
          the full blown CompareICStub for a stupid string comparison.
      
      BUG=
      
      Review URL: https://codereview.chromium.org/1355983003
      
      Cr-Commit-Position: refs/heads/master@{#30845}
      be04dd5c
    • chunyang.dai's avatar
      X87: [runtime] Replace COMPARE/COMPARE_STRONG with proper Object::Compare. · 9155967e
      chunyang.dai authored
      port 593c655a (r30816).
      
      original commit message:
      
          This removes the weird COMPARE and COMPARE_STRONG JavaScript builtins
          and replaces them with a proper C++ implementation in Object::Compare
          and appropriate wrappers Object::LessThan, Object::GreaterThan, and
          friends that are intended to be used by a true/false returning CompareIC
          in the future, as well as the interpreter.  As a short-term solution we
          provide %Compare and %Compare_Strong entry points for the current
          CompareIC that return the appropriate integer values expected by
          fullcodegen currently.
      
          Now the Abstract Relational Comparison is also using the correct
          ToPrimitive implementation, which properly supports @@toPrimitive.
      
      BUG=
      
      Review URL: https://codereview.chromium.org/1353343002
      
      Cr-Commit-Position: refs/heads/master@{#30844}
      9155967e
    • julien.gilli's avatar
      Add ScopeInfo constants to post-mortem metadata · 357e6b99
      julien.gilli authored
      mdb_v8, a post-mortem debugging tool for Node.js, allows users to
      inspect ScopeInfo structures in order to get more information about
      closures.
      
      Currently, it hardcodes the metadata it uses to find this information.
      This change allows it to get this metadata from the node binary itself,
      and thus to adapt to future changes made to the layout of the ScopeInfo
      data structure.
      
      BUG=
      
      R=bmeurer@chromium.org
      
      Review URL: https://codereview.chromium.org/1350843003
      
      Cr-Commit-Position: refs/heads/master@{#30843}
      357e6b99
    • littledan's avatar
      Implement sloppy-mode block-defined functions (Annex B 3.3) · e5ff10d7
      littledan authored
      ES2015 specifies very particular semantics for functions defined in blocks.
      In strict mode, it is simply a lexical binding scoped to that block. In sloppy
      mode, in addition to that lexical binding, there is a var-style binding in
      the outer scope, which is overwritten with the local binding when the function
      declaration is evaluated, *as long as* introducing ths var binding would not
      create a var/let conflict in the outer scope.
      
      This patch implements the semantics by introducing a DelegateStatement, which
      is initially filled in with the EmptyStatement and overwritten with the
      assignment when the scope is closed out and it can be checked that there is
      no conflict.
      
      This patch is tested with a new mjsunit test, and I tried staging it and running
      test262, finding that the tests that we have disabled due to lack of Annex B
      support now pass.
      
      R=adamk,rossberg
      LOG=Y
      BUG=v8:4285
      
      Review URL: https://codereview.chromium.org/1332873003
      
      Cr-Commit-Position: refs/heads/master@{#30842}
      e5ff10d7
  2. 20 Sep, 2015 1 commit
    • alph's avatar
      Reland of Make profiler no frame region detection code more robust [ia86/x64] · 4962bbb1
      alph authored
      Upon collection of the stack trace if the current PC falls into
      the frame building code, the top frame might be in a non-consistent
      state. That leads to some of the frames could be missing from the
      stack trace.
      
      The patch makes it check instructions under current PC and if they
      look like the frame setup/destroy code, it skips the entire sample.
      
      Support for x86/x64
      
      CG_INCLUDE_TRYBOTS=tryserver.v8:v8_linux64_msan_rel
      BUG=chromium:529931
      LOG=N
      
      Review URL: https://codereview.chromium.org/1348533005
      
      Cr-Commit-Position: refs/heads/master@{#30841}
      4962bbb1
  3. 19 Sep, 2015 1 commit
    • v8-autoroll's avatar
      Update V8 DEPS. · d44588a9
      v8-autoroll authored
      Rolling v8/build/gyp to cf3170e30578d600b8ec8cd68553cc5e606d42eb
      
      Rolling v8/tools/clang to 76e743dc622478312b66661ad48997b318628cbb
      
      TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org
      
      Review URL: https://codereview.chromium.org/1357793002
      
      Cr-Commit-Position: refs/heads/master@{#30840}
      d44588a9
  4. 18 Sep, 2015 26 commits
  5. 17 Sep, 2015 7 commits
    • mbrandy's avatar
      PPC: [runtime] Initial step towards switching Execution::Call to callable. · 05c804fc
      mbrandy authored
      Port d5bbd45f
      
      Original commit message:
          Currently Execution::Call (and friends) still duplicate a lot of the
          Call sequence logic that should be encapsulated in the Call and
          CallFunction builtins. So the plan now is to switch Execution::Call
          to accept any Callable and just pass that through to the Call builtin.
      
      R=bmeurer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, dstence@us.ibm.com
      BUG=v8:4413
      LOG=n
      
      Review URL: https://codereview.chromium.org/1347213003
      
      Cr-Commit-Position: refs/heads/master@{#30813}
      05c804fc
    • gdeepti's avatar
      [simdjs] Update spec version to 0.8.4 · a633a38f
      gdeepti authored
      Merge ShiftRightArithmetic and ShiftRightLogical Functions.
      
      BUG=v8:4124
      LOG=Y
      
      Review URL: https://codereview.chromium.org/1351663002
      
      Cr-Commit-Position: refs/heads/master@{#30812}
      a633a38f
    • rmcilroy's avatar
      [arm64]: Fix bug introduced accidentally in r30710 · 2088752c
      rmcilroy authored
      Uncomment the if (!serializer_enabled()) check which I accidentially left
      commented out after debugging during the CLs development.
      
      BUG=chromium:532969
      R=bmeurer@chromium.org
      LOG=n
      
      Review URL: https://codereview.chromium.org/1351943002
      
      Cr-Commit-Position: refs/heads/master@{#30811}
      2088752c
    • mbrandy's avatar
      PPC: [runtime] Replace the EQUALS builtin with proper Object::Equals. · 92eed98b
      mbrandy authored
      Port 54bab695
      
      Original commit message:
          Move the implementation of the Abstract Equality Comparison to the
          runtime and thereby remove the EQUALS dispatcher builtin. Also remove
          the various runtime entry points that were only used to support the
          EQUALS builtin.
      
          Now the Abstract Equality Comparison is also using the correct
          ToPrimitive implementation, which properly supports @@toPrimitive.
      
      R=bmeurer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, dstence@us.ibm.com
      BUG=v8:4307
      LOG=n
      
      Review URL: https://codereview.chromium.org/1357493002
      
      Cr-Commit-Position: refs/heads/master@{#30810}
      92eed98b
    • mbrandy's avatar
      PPC: [builtins] Unify the String constructor. · b82efa82
      mbrandy authored
      Port a3d6f6cc
      
      Original commit message:
          Implement the String constructor completely as native builtin,
          avoiding the need to do gymnastics in JavaScript builtin to
          properly detect the no argument case (which is different from
          the undefined argument case) and also allowing to just
          tailcall through to ToString or SymbolDescriptiveString for
          the common case. Also the JavaScript builtin was misleading
          since the case for construct call was unused, but could be
          triggered in a wrong way once we support tail calls from
          constructor functions.
      
          This refactoring allows us to properly implement subclassing
          for String builtins, once we have the correct initial_map on
          derived classes (it's merely a matter of using NewTarget
          instead of the target register now).
      
          This introduces a new %SymbolDescriptiveString runtime
          entry, which is also used by Symbol.toString() now.
      
      R=bmeurer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, dstence@us.ibm.com
      BUG=
      
      Review URL: https://codereview.chromium.org/1354663002
      
      Cr-Commit-Position: refs/heads/master@{#30809}
      b82efa82
    • bmeurer's avatar
      [runtime] Initial step towards switching Execution::Call to callable. · d5bbd45f
      bmeurer authored
      Currently Execution::Call (and friends) still duplicate a lot of the
      Call sequence logic that should be encapsulated in the Call and
      CallFunction builtins. So the plan now is to switch Execution::Call
      to accept any Callable and just pass that through to the Call builtin.
      
      CQ_INCLUDE_TRYBOTS=tryserver.v8:v8_linux_nosnap_dbg
      R=jarin@chromium.org
      BUG=v8:4413
      LOG=n
      
      Committed: https://crrev.com/359645f48156e15f235e9a9ede7910e0bcd9ae45
      Cr-Commit-Position: refs/heads/master@{#30791}
      
      Review URL: https://codereview.chromium.org/1353723002
      
      Cr-Commit-Position: refs/heads/master@{#30808}
      d5bbd45f
    • mbrandy's avatar
      PPC: Remove --pretenure-call-new · 632c3679
      mbrandy authored
      Port b5588f48
      
      Original commit message:
          There isn't a plan to turn it on soon, so we'll take it out in favor of cleaner code.
      
      R=mvstanton@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, dstence@us.ibm.com
      BUG=
      
      Review URL: https://codereview.chromium.org/1347253003
      
      Cr-Commit-Position: refs/heads/master@{#30807}
      632c3679