1. 20 Nov, 2017 28 commits
  2. 19 Nov, 2017 3 commits
  3. 18 Nov, 2017 4 commits
  4. 17 Nov, 2017 5 commits
    • Jakob Kummerow's avatar
      [bigint] Encapsulate internals in MutableBigInt · 977da550
      Jakob Kummerow authored
      This CL creates the invariant that the BigInt class treats
      BigInt objects as immutable. Writing to new BigInt objects
      as part of their construction is done by the MutableBigInt
      helper class, which in turn is hidden as an implementation
      detail in bigint.cc.
      As a side effect, this refactoring enforces right-trimming
      checks for all newly created BigInts, and ensures that all
      BigInt allocations possibly exceeding kMaxLength check for
      this case and throw a RangeError instead of crashing.
      
      Bug: v8:6791
      Tbr: mlippautz@chromium.org
      Change-Id: Id239746108e6b076b47a03ba37462001eb501507
      Reviewed-on: https://chromium-review.googlesource.com/742329
      Commit-Queue: Jakob Kummerow <jkummerow@chromium.org>
      Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49462}
      977da550
    • Ulan Degenbaev's avatar
      [runtime] Make layout descriptor helper safe for concurrent marking. · 61bf2cc6
      Ulan Degenbaev authored
      The layout descriptor helper computes the object header size using
      map->instance_size() and map->GetInObjectProperties().
      
      It races with finalization of slack tracking, which changes both
      the instance size and the in-object properties count.
      
      This patch replaces the in-object properties count byte in the map
      with the byte that stores the start offset of in-object properties.
      
      The new byte can be used in the layout descriptor to compute the
      object header size and it is immutable.
      
      This patch also renames InstanceSize to InstanceSizeInWords where
      the instance size is represented in words.
      
      Bug: chromium:786069, chromium:694255
      Change-Id: I4b48c6944d3fe8a950bd7b0ba43d75216b177a78
      Reviewed-on: https://chromium-review.googlesource.com/776720
      Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarIgor Sheludko <ishell@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49461}
      61bf2cc6
    • Igor Sheludko's avatar
      [runtime] Fix class literal instantiation. · ed53f05c
      Igor Sheludko authored
      Class' prototype temporarily got properies backing store inconsistent with
      the map which obviously confused heap verifier.
      
      Bug: v8:5799
      Change-Id: Ie28b0418daa657763d07c8a928851111680718ed
      Reviewed-on: https://chromium-review.googlesource.com/777560Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Commit-Queue: Igor Sheludko <ishell@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49460}
      ed53f05c
    • Pierre Langlois's avatar
      [perf-prof] Do not crash on BytecodeArray move events · 027cecdb
      Pierre Langlois authored
      The logger for perf does not support relocating code objects so as a result we
      disable code space compacting to make sure code does not move. However, a
      a CodeMove event may still happen if a BytecodeArray object moves, which isn't
      relevant to the perf jit support so we can ignore it.
      
      Bug: 
      Change-Id: Ie6acf58fe6adfb5cec2f8756f457134cf3b13c2a
      Reviewed-on: https://chromium-review.googlesource.com/759795Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
      Commit-Queue: Pierre Langlois <pierre.langlois@arm.com>
      Cr-Commit-Position: refs/heads/master@{#49459}
      027cecdb
    • Leszek Swirski's avatar
      [code-cache] Log resources with no cache handler · 25820bda
      Leszek Swirski authored
      Add another entry to the NoCacheReason enum, reporting that the chromium
      ScriptResource has no cache handler.
      
      Also, the amount of chromium-specific entries in this enum is getting
      too high. So, added a TODO for removing them -- possibly in the future
      we want to do this no-cache reason logging in Chromium after all,
      propagating isolate cache hits and consume failures back up the API with
      an out parameter.
      
      Bug: chromium:769203
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: I63ca863cfef61e04e7104318eb79810796b61a9c
      Reviewed-on: https://chromium-review.googlesource.com/776893Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49458}
      25820bda