1. 12 Oct, 2017 19 commits
  2. 11 Oct, 2017 21 commits
    • Jungshik Shin's avatar
      Revert "Enable icu-timezone-data by default" · 28ef8dc7
      Jungshik Shin authored
      This reverts commit d9a25842.
      
      Reason for revert: 
      
      I'm reverting this CL for a few reasons. #2 is the most significant and I should have thought of that before making a switch. Sorry for that.   
      
      1) perf-regression: http://crbug.com/769706
      2) http://crbug.com/612010 : ICU timezone update is not propagated to zygote process so that new tabs will hold on to an old timezone even after a timezone change on Linux and Chrome OS. 
      3) http://crbug.com/754053 : OS timezone detection issues on macOS 10.13, Ubutu 16, RHEL 7, SuSe Linux 12 or newer. ; it's being fixed. So, it actually ok.  
      4) http://crbug.com/771868 : timezone wrong in gmail: If it's due to #3, we're fine because it's fixed. If not, we need to look more.
      
      Original change's description:
      > Enable icu-timezone-data by default
      > 
      > This will introduce a new behavior on POSIX(-like) platforms. Timezone
      > names inside parentheses after GMT offset will not be 3-4 letter
      > abbreviation any longer. They'll be human-readable names in the current
      > default locale. This matches the current Windows behavior.
      > 
      > new Date(2017, 5, 22).toString()
      > new Date(2017, 11, 22).toString()
      > 
      > Current:
      > 
      > Thu Jun 22 2017 00:00:00 GMT-0700 (PDT)
      > Fri Dec 22 2017 00:00:00 GMT-0800 (PST)
      > 
      > New in en-US locale:
      > 
      > Thu Jun 22 2017 00:00:00 GMT-0700 (Pacific Daylight Time)
      > Fri Dec 22 2017 00:00:00 GMT-0800 (Pacific Standard Time)
      > 
      > New in German locale:
      > 
      > Thu Jun 22 2017 00:00:00 GMT-0700 (Nordamerikanische Westküsten-Sommerzeit)
      > Fri Dec 22 2017 00:00:00 GMT-0800 (Nordamerikanische Westküsten-Normalzeit)
      > 
      > BUG=v8:6031, v8:2137, v8:6076
      > TEST=mjsunit/icu-date-lord-howe.js, mjsunit/icu-date-to-string.js
      > 
      > Change-Id: I4e7fd8b3ddae5c7779e220c4c101e45904fcdc01
      > Reviewed-on: https://chromium-review.googlesource.com/625164
      > Commit-Queue: Jungshik Shin <jshin@chromium.org>
      > Reviewed-by: Daniel Ehrenberg <littledan@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#47953}
      
      TBR=adamk@chromium.org,littledan@chromium.org,jshin@chromium.org
      
      # Not skipping CQ checks because original CL landed > 1 day ago.
      
      Bug: v8:6031, v8:2137, v8:6076, chromium:769706, chromium:612010, chromium:771868
      Change-Id: I60d75467ee21975d3a235344b01c0d2d44a7da96
      Reviewed-on: https://chromium-review.googlesource.com/713404Reviewed-by: 's avatarAdam Klein <adamk@chromium.org>
      Commit-Queue: Jungshik Shin <jshin@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48478}
      28ef8dc7
    • Alexey Kozyatinskiy's avatar
      Roll third_party/inspector_protocol to 8cb7a4f50ff7d5b1b7f2e5df0542dc577c88bdc3 · 744b49ef
      Alexey Kozyatinskiy authored
      This roll includes:
      - [inspector_protocol] fixed compatibility with latest jinja 2.9.6
      - [inspector_protocol] removed unused variable
      - Follow up on alph's review comments.
      - Provide default escape implementation for latin and wide strings.
      - Allow escaping utf8 strings in embedders that operate std::string.
      - Upload inspector_protocol changes to Gerrit by default
      - [inspector_protocol] Fix building with non-ASCII paths
      - [inspector_protocol] added StringUtil::toDouble method as requirement
      - Add const char* overloads to ErrorSupport
      
      BUG=chromium:743313
      R=dgozman@chromium.org
      
      Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel
      Change-Id: Ic81a62c638bf592ae65c84055d53d926e50715ac
      Reviewed-on: https://chromium-review.googlesource.com/713538Reviewed-by: 's avatarDmitry Gozman <dgozman@chromium.org>
      Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48477}
      744b49ef
    • John Barboza's avatar
      PPC/s390: Delete ObjectTriple and support code · a445b97c
      John Barboza authored
      Port fc413158
      
      Original Commit Message:
      
          ObjectTriple isn't used since f1ec44e2. Delete
          it, and simplify CEntryStub on all backends.
      
      R=martyn.capewell@arm.com, joransiu@ca.ibm.com, jyan@ca.ibm.com, bjaideep@ca.ibm.com, michael_dawson@ca.ibm.com
      BUG=
      LOG=N
      
      Change-Id: I4897783bb848e016d93731585e6891033fa4d4cf
      Reviewed-on: https://chromium-review.googlesource.com/714022Reviewed-by: 's avatarJunliang Yan <jyan@ca.ibm.com>
      Commit-Queue: Junliang Yan <jyan@ca.ibm.com>
      Cr-Commit-Position: refs/heads/master@{#48476}
      a445b97c
    • Aseem Garg's avatar
      [wasm] Add uma stat for wasm lazy throughput · 9fdb8c82
      Aseem Garg authored
      This CL adds an uma stat to track the throughput
      of lazy compilation for wasm functions in KB/s.
      
      BUG=chromium:770618
      R=kschimpf@chromium.org,bradnelson@chromium.org,isherman@chromium.org
      
      Change-Id: Iad06cfb1f185f7e2ab6b0198282c03c3d8f29e2e
      Reviewed-on: https://chromium-review.googlesource.com/706276
      Commit-Queue: Aseem Garg <aseemgarg@chromium.org>
      Reviewed-by: 's avatarClemens Hammacher <clemensh@chromium.org>
      Reviewed-by: 's avatarBrad Nelson <bradnelson@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48475}
      9fdb8c82
    • Eric Holk (eholk)'s avatar
      Reland "Reland "[wasm] trap handlers: fall back on old signal handler"" · 1117da83
      Eric Holk (eholk) authored
      This is a reland of cc237d87
      Original change's description:
      > Reland "[wasm] trap handlers: fall back on old signal handler"
      > 
      > This is a reland of ee4fe896
      > Original change's description:
      > > [wasm] trap handlers: fall back on old signal handler
      > > 
      > > This is primarily needed to test D8 under ASan. ASan installs a signal handler
      > > early in the process startup to show stack traces from crashes. We need to make
      > > sure that if V8 does not handle a signal then the existing handler gets a
      > > chance.
      > > 
      > > This change only applies when using V8's default signal handler. When
      > > integrating with the embedder's signal handler the behavior is unchanged.
      > > 
      > > Bug: chromium:771948
      > > Change-Id: Ifd560acf9700ec5f714f009530258fa92c83cabe
      > > Reviewed-on: https://chromium-review.googlesource.com/705823
      > > Reviewed-by: Deepti Gandluri <gdeepti@chromium.org>
      > > Commit-Queue: Eric Holk <eholk@chromium.org>
      > > Cr-Commit-Position: refs/heads/master@{#48429}
      > 
      > Bug: chromium:771948
      > Change-Id: Ide307091c432fd933c48f89c51851b8dce44dd30
      > Reviewed-on: https://chromium-review.googlesource.com/710114
      > Reviewed-by: Deepti Gandluri <gdeepti@chromium.org>
      > Commit-Queue: Eric Holk <eholk@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#48435}
      
      Bug: chromium:771948
      Change-Id: I781dfe356a728760090b6ccfa58212096e8f20c8
      Reviewed-on: https://chromium-review.googlesource.com/713956Reviewed-by: 's avatarDeepti Gandluri <gdeepti@chromium.org>
      Commit-Queue: Eric Holk <eholk@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48474}
      1117da83
    • John Barboza's avatar
      PPC/s390: [arm64] Pair some pushes and delete unused code · 61a23faa
      John Barboza authored
      Port 193dcf76
      
      Original Commit Message:
      
          Pair some stack ops so that they deal with an even numbers of registers, add
          padding around profile entry calls, and delete some unused macro assembler code.
      
      R=martyn.capewell@arm.com, joransiu@ca.ibm.com, jyan@ca.ibm.com, bjaideep@ca.ibm.com, michael_dawson@ca.ibm.com
      BUG=
      LOG=N
      
      Change-Id: I017ccc699839b04bc7295d00c45e315f7cf074c1
      Reviewed-on: https://chromium-review.googlesource.com/713996Reviewed-by: 's avatarJunliang Yan <jyan@ca.ibm.com>
      Reviewed-by: 's avatarJoran Siu <joransiu@ca.ibm.com>
      Commit-Queue: Junliang Yan <jyan@ca.ibm.com>
      Cr-Commit-Position: refs/heads/master@{#48473}
      61a23faa
    • Wez's avatar
      Disable querying of CPU info under ARM64. · d567f413
      Wez authored
      There are currently no decisions based on the CPU implementor, variant
      or part values for ARM64, and the code to fetch those values was not
      compatible with Fuchsia/ARM64.
      
      Bug: chromium:772031
      Change-Id: I2305fc7a97d8c0a24bb0ad115447665976e5814a
      Reviewed-on: https://chromium-review.googlesource.com/706642Reviewed-by: 's avatarBenedikt Meurer <bmeurer@chromium.org>
      Reviewed-by: 's avatarRodolph Perfetta <rodolph.perfetta@arm.com>
      Commit-Queue: Wez <wez@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48472}
      d567f413
    • Jakob Kummerow's avatar
      [bigint] Support BigInts in <<,>>,>>>,&,|,^ binary ops · 15609882
      Jakob Kummerow authored
      This CL teaches the respective bytecode handlers and standalone
      stubs about BigInts, and collects "kBigInt" type feedback for them.
      Just like for other binary ops, that feedback is converted to "any"
      for TurboFan for now.
      
      Bug: v8:6791
      Change-Id: I0709cc77dc248dad506207c7b35b63c80b1ef96a
      Reviewed-on: https://chromium-review.googlesource.com/699424Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
      Reviewed-by: 's avatarAdam Klein <adamk@chromium.org>
      Commit-Queue: Jakob Kummerow <jkummerow@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48471}
      15609882
    • Leszek Swirski's avatar
      [ignition] Fix AST printing to print eager inner literals · 6576495f
      Leszek Swirski authored
      AST printing was printing the literal of the ParseInfo, which is the
      current function being parsed. However, for eager compilation of inner
      literals, this may not be the function being compiled, which is in the
      CompilationInfo.
      
      So, for --print-ast, we have to get the FunctionLiteral from
      CompilationInfo.
      
      Bug: chromium:771653
      Change-Id: I2088e1f1f7b8a3d664aae65cab699a641e5fd302
      Reviewed-on: https://chromium-review.googlesource.com/712354Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48470}
      6576495f
    • Tobias Tebbi's avatar
      Reland^3 "[turbofan] eagerly prune None types and deadness from the graph" · 4cf47645
      Tobias Tebbi authored
      This fixes the issues 
      https://bugs.chromium.org/p/chromium/issues/detail?id=772873 
      and https://bugs.chromium.org/p/chromium/issues/detail?id=772872.
      
      One problem was that mutating an effect node into Unreachable confused 
      the LoadElimination sidetables, so I just always create a new node now.
      
      The other problem was that UpdateBlockControl() was executed after 
      UpdateEffectPhi() in the lazy case. This reverted the update to the Merge input.
      So now I make sure that UpdateEffectPhi() is always executed last.
      
      This is a reland of 6ddb5e7d
      Original change's description:
      > Reland^2 "[turbofan] eagerly prune None types and deadness from the graph"
      > 
      > Now, the EffectControlLinearizer connects all occurrences of Unreachable to the 
      > graph end. This fixes issues with later phases running DeadCodeElimination and
      > introducing new DeadValue nodes when processing uses of Unreachable.
      > 
      > This is a reland of 3c4bc27f
      > Original change's description:
      > > Reland "[turbofan] eagerly prune None types and deadness from the graph"
      > > 
      > > This is a reland of e1cdda25
      > > Original change's description:
      > > > [turbofan] eagerly prune None types and deadness from the graph
      > > > 
      > > > In addition to using the {Dead} node to prune dead control nodes and nodes that 
      > > > depend on them, we introduce a {DeadValue} node representing an impossible value 
      > > > that can occur at any position in the graph. The extended {DeadCodeElimination}
      > > > prunes {DeadValue} and its uses, inserting a crashing {Unreachable} node into
      > > > the effect chain when possible. The remaining uses of {DeadValue} are handled
      > > > in {EffectControlLinearizer}, where we always have access to the effect chain.
      > > > In addition to explicitly introduced {DeadValue} nodes, we consider any value use
      > > > of a node with type {None} as dead.
      > > > 
      > > > Bug: chromium:741225
      > > > Change-Id: Icc4b636d1d018c452ba1a2fa7cd3e00e522f1655
      > > > Reviewed-on: https://chromium-review.googlesource.com/641250
      > > > Commit-Queue: Tobias Tebbi <tebbi@chromium.org>
      > > > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
      > > > Cr-Commit-Position: refs/heads/master@{#48208}
      > > 
      > > Bug: chromium:741225
      > > Change-Id: I21316913dae02864f7a6d7c9269405a79f054138
      > > Reviewed-on: https://chromium-review.googlesource.com/692034
      > > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
      > > Commit-Queue: Tobias Tebbi <tebbi@chromium.org>
      > > Cr-Commit-Position: refs/heads/master@{#48232}
      > 
      > Bug: chromium:741225
      > Change-Id: I5702ec34856c075717162153adc765774453c45f
      > Reviewed-on: https://chromium-review.googlesource.com/702264
      > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
      > Commit-Queue: Tobias Tebbi <tebbi@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#48366}
      
      Bug: chromium:741225
      Change-Id: I4054a694d2521c2e1f0c4a3ad0f3cf100b5c536f
      Reviewed-on: https://chromium-review.googlesource.com/709214
      Commit-Queue: Tobias Tebbi <tebbi@chromium.org>
      Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48469}
      4cf47645
    • Jan Krems's avatar
      Reland "[modules] Implement import.meta proposal" · 1c552999
      Jan Krems authored
      This is a reland of ed6f00fb
      Original change's description:
      > [modules] Implement import.meta proposal
      > 
      > Rewrites references to import.meta to a new GetImportMetaObject runtime
      > call. Embedders can define a callback for creating the meta object using
      > v8::Isolate::SetHostGetImportMetaObjectCallback. If no callback has been
      > provided, an empty object with null prototype is created.
      > 
      > This adds an example implementation to d8 that sets meta.url.
      > 
      > Bug: v8:6693
      > Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      > Change-Id: I6871eec79da45bba81bbbc84b1ffff48534c368d
      > Reviewed-on: https://chromium-review.googlesource.com/707902
      > Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org>
      > Reviewed-by: Adam Klein <adamk@chromium.org>
      > Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#48433}
      
      TBR=adamk@chromium.org
      
      Bug: v8:6693
      Change-Id: Ie2d746ad996a56ed6ff50b832f320fe44e02f231
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Reviewed-on: https://chromium-review.googlesource.com/712834Reviewed-by: 's avatarSathya Gunasekaran <gsathya@chromium.org>
      Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48468}
      1c552999
    • Michael Achenbach's avatar
      [test] Remove deprecated test-download feature · 14bfa18b
      Michael Achenbach authored
      Bug: v8:6917
      Change-Id: I3889cd0d059c3473a7b83eb298734a7a6a8a1de5
      Reviewed-on: https://chromium-review.googlesource.com/712175Reviewed-by: 's avatarSergiy Byelozyorov <sergiyb@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48467}
      14bfa18b
    • Eric Holk's avatar
      Revert "Track committed array buffer size rather than allocation length" · 83103bce
      Eric Holk authored
      This reverts commit b0ced926.
      
      Reason for revert: Build breakage - https://build.chromium.org/p/client.v8/builders/V8%20Linux/builds/20832
      
      Original change's description:
      > Track committed array buffer size rather than allocation length
      > 
      > WebAssembly creates ArrayBuffers with large allocations where only a small
      > amount is committed. The uncommitted address space should not be counted as used
      > memory. Doing so can lead to the GC spending unnecessary time collecting memory
      > when there is not really pressure.
      > 
      > Bug: 
      > Change-Id: Ife7b84e9858e87faabc360a61f887b2fda6d99db
      > Reviewed-on: https://chromium-review.googlesource.com/710227
      > Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
      > Commit-Queue: Eric Holk <eholk@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#48462}
      
      TBR=mlippautz@chromium.org,eholk@chromium.org
      
      Change-Id: Ib7b28a7bbc8ffc11e0bf8c4bb16b2da61cbdbd5f
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Reviewed-on: https://chromium-review.googlesource.com/712835Reviewed-by: 's avatarEric Holk <eholk@chromium.org>
      Commit-Queue: Eric Holk <eholk@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48466}
      83103bce
    • Georgia Kouveli's avatar
      [arm64] Update BuiltinContinuation frames for jssp alignment. · a63f045c
      Georgia Kouveli authored
      Adds some necessary padding to ensure the frame is 16-byte aligned.
      We don't yet consider the bailout state, which will be handled separately.
      
      This patch also improves the code generated for ContinueTo*Builtin* stubs.
      
      Finally, it adds a test that checks the return value for Array.map in
      the case where a LAZY deopt results in a topmost builtin continuation
      frame - this is easy to break if the padding for the result is done
      incorrectly in NotifyBuiltinContinuation, but was not detected by existing
      tests.
      
      Bug: v8:6644
      Change-Id: Id1a294950cdf535e2bfdb0ed27c67f077ec34f8a
      Reviewed-on: https://chromium-review.googlesource.com/704835
      Commit-Queue: Georgia Kouveli <georgia.kouveli@arm.com>
      Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48465}
      a63f045c
    • Clemens Hammacher's avatar
      [wasm] [trap-handler] Report correct code size · a7abde7c
      Clemens Hammacher authored
      Instead of using the size of the whole code object, just use the size
      of the instructions, because only there faults can happen.
      
      R=eholk@chromium.org
      
      Bug: v8:5277
      Change-Id: Ia5768891ec3c1ee5ad8affc9486e044d79e23146
      Reviewed-on: https://chromium-review.googlesource.com/712536Reviewed-by: 's avatarEric Holk <eholk@chromium.org>
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48464}
      a7abde7c
    • Andreas Rossberg's avatar
      [wasm] [multival] Reland: Allow function types as block types · 5d3dfc85
      Andreas Rossberg authored
      Only change over original: Init sig_index to 0 at
      function-body-decoder-impl.h:168, to make MSAN happy on error path.
      
      R=titzer@chromium.org
      
      Change-Id: I9ac17215360523b656b10d2466201001b65992c0
      Reviewed-on: https://chromium-review.googlesource.com/712655Reviewed-by: 's avatarBen Titzer <titzer@chromium.org>
      Commit-Queue: Andreas Rossberg <rossberg@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48463}
      5d3dfc85
    • Eric Holk's avatar
      Track committed array buffer size rather than allocation length · b0ced926
      Eric Holk authored
      WebAssembly creates ArrayBuffers with large allocations where only a small
      amount is committed. The uncommitted address space should not be counted as used
      memory. Doing so can lead to the GC spending unnecessary time collecting memory
      when there is not really pressure.
      
      Bug: 
      Change-Id: Ife7b84e9858e87faabc360a61f887b2fda6d99db
      Reviewed-on: https://chromium-review.googlesource.com/710227Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Commit-Queue: Eric Holk <eholk@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48462}
      b0ced926
    • Michael Achenbach's avatar
      [build] Check out instrumented libraries via gclient flag · 1a4d84f4
      Michael Achenbach authored
      Prepared by:
      https://chromium-review.googlesource.com/c/chromium/tools/build/+/712036
      
      Bug: chromium:772804
      Change-Id: Ib6ace7510962e5f00008c2f2c5f87f339363d995
      Reviewed-on: https://chromium-review.googlesource.com/708258Reviewed-by: 's avatarSergiy Byelozyorov <sergiyb@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48461}
      1a4d84f4
    • Michael Achenbach's avatar
      [test] Temporary output for investigation · b269c146
      Michael Achenbach authored
      Currently it's hard to reason about the hung tests on worker processes.
      This adds simple output when we're trying to kill a hung process.
      
      Change-Id: Iae5e14dac70a8149c074043dd00cbf10e4d5f3de
      Reviewed-on: https://chromium-review.googlesource.com/712455Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48460}
      b269c146
    • Pierre Langlois's avatar
      [cctest] Record execution of parallel moves. · dabd1c0a
      Pierre Langlois authored
      This patch is a first step towards target independent tests for the
      CodeGenerator's AssembleMove and AssembleSwap methods.
      
      The tests on top of which this builds would only make sure that no assertions
      were triggered while generating moves, and that the hardware is happy executing
      them. We want to do more and check that the generated code performs correctly.
      
      In a nutshell, this introduces a facility that can do the following:
      
        - Setup an environment with registers and stack slots initialised with random
          values.
        - Perform a list of randomly generated moves and/or swaps on those.
        - Return the resulting environment.
      
      This is a first step and therefore is lacking a few things which will be
      implemented as follow-ups:
      
        - Support for kSimd128 moves and swaps.
        - Support large offsets for stack moves, as well as positive and negative.
        - Compare the resulting environment against the result of a reference
          simulation.
      
      For more background information, see this design document:
      https://docs.google.com/document/d/1KpioxCmtiB_9RaPaRidZPVtKlZ2BaNKGPYUjKFihhK0
      
      Bug: v8:6848
      Change-Id: Ie7dc837f4444df010ab58c64b722d40ee5d2af72
      Reviewed-on: https://chromium-review.googlesource.com/677398Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
      Reviewed-by: 's avatarBill Budge <bbudge@chromium.org>
      Commit-Queue: Pierre Langlois <pierre.langlois@arm.com>
      Cr-Commit-Position: refs/heads/master@{#48459}
      dabd1c0a
    • Ulan Degenbaev's avatar
      [heap] Disable map retaining optimization. · 00ba1dca
      Ulan Degenbaev authored
      The optimization keeps dying maps alive for several GCs to mitigate
      code deoptimization with weak maps.
      
      This patch disables the optimization to see if it still needed.
      
      Bug: 
      Change-Id: Ie5717967ad56858e6ae546c90fde73e8d5bcc4ec
      Reviewed-on: https://chromium-review.googlesource.com/712598Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48458}
      00ba1dca