1. 21 Sep, 2017 21 commits
  2. 20 Sep, 2017 13 commits
  3. 19 Sep, 2017 6 commits
    • Bill Budge's avatar
      Reland "[Memory] Move VirtualMemory out of base:: platform." · f2cd10db
      Bill Budge authored
      This is a reland of 4dd293d9
      Original change's description:
      > [Memory] Move VirtualMemory out of base:: platform.
      > 
      > - Moves base::VirtualMemory to v8::internal::VirtualMemory.
      > - Makes VirtualMemory platform-independent by moving internals to new
      >   OS:: static methods, for each platform.
      > 
      > This will make it easier to delegate memory management in VirtualMemory
      > to V8::Platform, so that embedders like Blink can override it. We can't
      > depend on V8::Platform in base/platform.
      > 
      > Bug: chromium:756050
      > Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      > Change-Id: Iadfe230b6850bd917727a373f277afded9883adf
      > Reviewed-on: https://chromium-review.googlesource.com/653214
      > Commit-Queue: Bill Budge <bbudge@chromium.org>
      > Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#48048}
      
      Bug: chromium:756050
      Change-Id: Ib492c7c69f1833be127a571808301e96b84b8aa2
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Reviewed-on: https://chromium-review.googlesource.com/671125
      Commit-Queue: Bill Budge <bbudge@chromium.org>
      Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48084}
      f2cd10db
    • Jaroslav Sevcik's avatar
      Revert "[Turbofan] Array.prototype.filter inlining." · 47b63806
      Jaroslav Sevcik authored
      This reverts commit 37aa13fe.
      
      Reason for revert: Suspected to break 63.0.3219 Canary
      
      Original change's description:
      > [Turbofan] Array.prototype.filter inlining.
      > 
      > Support inlining of Array.prototype.filter in TurboFan.
      > 
      > Bug: v8:1956
      > Change-Id: Iba4d683aaa86c6104e8a1cf4d0f549a0c516576a
      > Reviewed-on: https://chromium-review.googlesource.com/657021
      > Commit-Queue: Michael Stanton <mvstanton@chromium.org>
      > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#48040}
      
      TBR=mvstanton@chromium.org,mstarzinger@chromium.org
      
      # Not skipping CQ checks because original CL landed > 1 day ago.
      
      Bug: v8:1956
      Change-Id: I125a8caf128890d788e040adfe2fc76bd8d1fbea
      Reviewed-on: https://chromium-review.googlesource.com/672783Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
      Reviewed-by: 's avatarMichael Stanton <mvstanton@chromium.org>
      Commit-Queue: Jaroslav Sevcik <jarin@chromium.org>
      Commit-Queue: Michael Stanton <mvstanton@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48083}
      47b63806
    • Jaroslav Sevcik's avatar
      [profiler] Do not log timer events when --prof is specified. · 77836fec
      Jaroslav Sevcik authored
      Now hopefully getting it right, but still leaving in the confusing
      flag implications.
      
      Bug: v8:6520,chromium:766162
      Change-Id: Idc6dca012bf0c9777b4a75cf424410ce5914c885
      Reviewed-on: https://chromium-review.googlesource.com/671022Reviewed-by: 's avatarCamillo Bruni <cbruni@chromium.org>
      Commit-Queue: Jaroslav Sevcik <jarin@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48082}
      77836fec
    • Mythri's avatar
      Change runtime_profiler to use bytecode array length · 807d0abe
      Mythri authored
      Runtime profiler uses bytecode array size for the tiering up decisions.
      Bytecode array size includes the header size as well. Inlining
      heuristics use bytecode array length instead. Bytecode array length
      is just the size of bytecode not inlcuding any headers. This change
      is to keep both of them in sync to avoid confusion. Also, the header
      contains several pointers and hence the size changes depending on the
      size of kPointerSize.
      
      Bug: 
      Change-Id: I22a9cf5e0bb9d6853c6a8be8d69c9ff459418a0d
      Reviewed-on: https://chromium-review.googlesource.com/670724Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
      Commit-Queue: Mythri Alle <mythria@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48081}
      807d0abe
    • Clemens Hammacher's avatar
      [cleanup] [wasm] Fix (D)CHECK macros · 2d75dd9b
      Clemens Hammacher authored
      Use the (D)CHECK_{EQ,NE,GT,...} macros instead of (D)CHECK with an
      embedded comparison. This gives better error messages and also does the
      right comparison for signed/unsigned mismatches.
      
      This will allow us to reenable the readability/check cpplint check.
      
      R=ahaas@chromium.org
      
      Bug: v8:6837
      Change-Id: Ic8966dfeacf02b2684eeef23fde99ec2be4ed81e
      Reviewed-on: https://chromium-review.googlesource.com/671364
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48080}
      2d75dd9b
    • Clemens Hammacher's avatar
      [cleanup] Fix (D)CHECK macros in src/regexp · 447af335
      Clemens Hammacher authored
      Use the (D)CHECK_{EQ,NE,GT,...} macros instead of (D)CHECK with an
      embedded comparison. This gives better error messages and also does the
      right comparison for signed/unsigned mismatches.
      
      This will allow us to reenable the readability/check cpplint check.
      
      R=jgruber@chromium.org
      
      Bug: v8:6837
      Change-Id: I9c489ac0e1b15fd4789c37fd32c9d3c76121a288
      Reviewed-on: https://chromium-review.googlesource.com/671343
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48079}
      447af335