1. 12 Aug, 2016 3 commits
  2. 07 Aug, 2016 1 commit
    • ulan's avatar
      Unify memory optimization modes and flags. · 6cebf7d9
      ulan authored
      This patch folds --optimize-for-size flag and check for low-memory device
      into Heap::ShouldOptimizeForMemoryUsage() predicate.
      
      It has the following side effects:
      - the heap growing factor for low-memory devices is capped at 1.3 (old value was 2.0).
      - the memory reducer will be more aggressive for low-memory devices.
      
      BUG=chromium:634900
      
      Review-Url: https://codereview.chromium.org/2218703004
      Cr-Commit-Position: refs/heads/master@{#38406}
      6cebf7d9
  3. 05 Aug, 2016 3 commits
  4. 04 Aug, 2016 2 commits
  5. 03 Aug, 2016 2 commits
    • jgruber's avatar
      Move NoSideEffectToString to C++ · d48170db
      jgruber authored
      BUG=
      
      Review-Url: https://codereview.chromium.org/2206573002
      Cr-Commit-Position: refs/heads/master@{#38289}
      d48170db
    • neis's avatar
      [debug] Don't notify listener of exceptions internal to a desugaring. · f813494f
      neis authored
      In the parser, we desugar yield* with the help of a regular yield. One
      particular implementation detail of this desugaring is that when the user calls
      the generator's throw method, this throws an exception that we immediately
      catch. This exception should not be visible to the user, but through Devtools'
      "Pause on Caught Exceptions" feature it used to be.
      
      This CL extends the type of catch predictions with a new value for such internal
      exceptions and uses that for the offending try-catch statement in yield*.  It
      instruments the debugger to _not_ trigger an exception event in that case.
      
      R=yangguo@chromium.org
      TBR=littledan@chromium.org
      BUG=v8:5218
      
      Review-Url: https://codereview.chromium.org/2203803002
      Cr-Commit-Position: refs/heads/master@{#38286}
      f813494f
  6. 02 Aug, 2016 1 commit
  7. 01 Aug, 2016 2 commits
  8. 26 Jul, 2016 2 commits
  9. 22 Jul, 2016 3 commits
  10. 21 Jul, 2016 4 commits
  11. 20 Jul, 2016 3 commits
  12. 19 Jul, 2016 2 commits
    • jgruber's avatar
      Move Error methods to C++ · 5742da05
      jgruber authored
      This ports a large portion of Error methods to C++,
      including the constructor, stack setter and getter,
      and Error.prototype.toString.
      
      BUG=
      
      Review-Url: https://codereview.chromium.org/2142933003
      Cr-Commit-Position: refs/heads/master@{#37870}
      5742da05
    • ahaas's avatar
      [builtins] Introduce a builtin for Abort(). · 9be015a2
      ahaas authored
      Calling Runtime::kAbort through a builtin instead of the c-entry stub
      will allow to generate the call in a background thread, because a
      builtin provides its own handle, whereas a code stub does not.
      
      @v8-mips-ports: Could you take a special look at the padding that is
      done in MacroAssembler::Abort()?
      
      R=bmeurer@chromium.org, titzer@chromium.org, mstarzinger@chromium.org, v8-mips-ports@googlegroups.com, v8-arm-ports@googlegroups.com
      
      Review-Url: https://codereview.chromium.org/2156923002
      Cr-Commit-Position: refs/heads/master@{#37854}
      9be015a2
  13. 18 Jul, 2016 2 commits
  14. 14 Jul, 2016 2 commits
    • jochen's avatar
      Revert of Reland "Don't compile functions in a context the caller doesn't have... · 63449d21
      jochen authored
      Revert of Reland "Don't compile functions in a context the caller doesn't have access to" (patchset #4 id:60001 of https://codereview.chromium.org/2143893005/ )
      
      Reason for revert:
      blink is unhappy about the microtask change
      
      Original issue's description:
      > Reland "Don't compile functions in a context the caller doesn't have access to"
      >
      > Original issue's description:
      > > Don't compile functions in a context the caller doesn't have access to
      > >
      > > Instead just return undefined
      > >
      > > A side effect of this is that it's no longer possible to compile
      > > functions in a detached context.
      > >
      > > BUG=chromium:541703
      > > R=verwaest@chromium.org,bmeurer@chromium.org
      >
      > BUG=chromium:541703
      > R=verwaest@chromium.org
      >
      > Committed: https://crrev.com/6bceabac5b705b2ce1f52d34650cea1ae3b8c617
      > Cr-Commit-Position: refs/heads/master@{#37756}
      
      TBR=verwaest@chromium.org
      # Skipping CQ checks because original CL landed less than 1 days ago.
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      BUG=chromium:541703
      
      Review-Url: https://codereview.chromium.org/2151843002
      Cr-Commit-Position: refs/heads/master@{#37760}
      63449d21
    • jochen's avatar
      Reland "Don't compile functions in a context the caller doesn't have access to" · 6bceabac
      jochen authored
      Original issue's description:
      > Don't compile functions in a context the caller doesn't have access to
      >
      > Instead just return undefined
      >
      > A side effect of this is that it's no longer possible to compile
      > functions in a detached context.
      >
      > BUG=chromium:541703
      > R=verwaest@chromium.org,bmeurer@chromium.org
      
      BUG=chromium:541703
      R=verwaest@chromium.org
      
      Review-Url: https://codereview.chromium.org/2143893005
      Cr-Commit-Position: refs/heads/master@{#37756}
      6bceabac
  15. 13 Jul, 2016 1 commit
  16. 12 Jul, 2016 1 commit
  17. 11 Jul, 2016 2 commits
  18. 08 Jul, 2016 1 commit
  19. 06 Jul, 2016 1 commit
  20. 04 Jul, 2016 1 commit
    • jgruber's avatar
      [builtins] Add receiver to builtin exit frames · f59a2335
      jgruber authored
      Stack trace generation requires access to the receiver; and while the
      receiver is already on the stack, we cannot determine its position
      during stack trace generation (it's stored in argv[0], and argc is only
      stored in a callee-saved register).
      
      This patch grants access to the receiver by pushing argc onto builtin
      exit frames as an extra argument. Compared to simply pushing the
      receiver, this requires an additional dereference during stack trace
      generation, but one fewer during builtin calls.
      
      BUG=v8:4815
      
      Review-Url: https://codereview.chromium.org/2106883003
      Cr-Commit-Position: refs/heads/master@{#37500}
      f59a2335
  21. 30 Jun, 2016 1 commit
    • jgruber's avatar
      [builtins] New frame type for exits to C++ builtins · 5febc27b
      jgruber authored
      Prior to this commit, calls to C++ builtins created standard exit
      frames, which are skipped when constructing JS stack traces. In order to
      show these calls on traces, we introduce a new builtin exit frame type.
      
      Builtin exit frames contain target and new.target on the stack and are
      not skipped during stack trace construction.
      
      BUG=v8:4815
      R=bmeurer@chromium.org, yangguo@chromium.org
      CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_chromium_rel_ng;tryserver.blink:linux_blink_rel;tryserver.v8:v8_linux_nosnap_dbg
      
      Committed: https://crrev.com/3c60c6b105f39344f93a8407f41534e5e60cf19a
      Review-Url: https://codereview.chromium.org/2090723005
      Cr-Original-Commit-Position: refs/heads/master@{#37384}
      Cr-Commit-Position: refs/heads/master@{#37416}
      5febc27b