- 14 Sep, 2020 3 commits
-
-
Almothana Athamneh authored
NOTRY=true Bug: chromium:1126457 Change-Id: I08df6070586cdc435595ddda74e1e8cfe2abf2b7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2401423 Commit-Queue: Almothana Athamneh <almuthanna@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Liviu Rau <liviurau@chromium.org> Cr-Commit-Position: refs/heads/master@{#69863}
-
Camillo Bruni authored
Stress configurations cause maps to be GC'ed too early. We now keep them alive by storing the object in a global variable. Bug: v8:10892 Change-Id: If03c42612d9907b3b6d0df8bb2de879857a89e0a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2404774Reviewed-by:
Georg Neis <neis@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#69862}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/d01f3c3..dc90e7d TBR=machenbach@chromium.org,tmrts@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I7e0cfda5b01f6a35ab869965087ad26524474415 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2407137Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#69861}
-
- 13 Sep, 2020 2 commits
-
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/db4df0f..d01f3c3 TBR=machenbach@chromium.org,tmrts@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Iddb6c36450238243b29bf8e49f9695c6b333d620 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2408129Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/349143e..db4df0f TBR=machenbach@chromium.org,tmrts@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Ie89554bf1e2f1955ab3dd989c9123dda8bbbd45d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2408294Reviewed-by:
-
- 12 Sep, 2020 1 commit
-
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/b3e63d3..349143e Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/13bf125..e53ee0c Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/fb6d901..a1e1549 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/97d6ab3..bf815f1 TBR=machenbach@chromium.org,tmrts@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I3a0ebbea978c6b54047998f5852ec3c1965b916c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2407492Reviewed-by:
-
- 11 Sep, 2020 28 commits
-
-
Ng Zhi An authored
Bug: v8:10180 Bug: v8:10501 Change-Id: I92700c2367aecb9eb5adf2a7c8d863815bbfe6ec Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2404459Reviewed-by:
Bill Budge <bbudge@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#69857}
-
Ng Zhi An authored
We need to construct Float32 nodes for f32x4, using Word32 operators will cause the wrong register to be allocated, triggering a CHECK failure. Bug: v8:10507 Change-Id: I70842f1d61b90fed2407ee52af4bc5a6b1b82ba6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2399050Reviewed-by:
-
Ng Zhi An authored
F32x4 and F64x2 pmin and pmax were accepted into the proposal [0], this removes all the ifdefs and todo guarding the prototypes, and moves these instructions out of the post-mvp flag. [0] https://github.com/WebAssembly/simd/pull/122 Bug: v8:10904 Change-Id: I4e0c2f29ddc5d7fc19a209cd02b3d369617574a0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2405802Reviewed-by:
-
Etienne Pierre-doray authored
Dynamic index generation used as starting seend boosts performance for Jobs that have many work items. This is taken from https://source.chromium.org/chromium/chromium/src/+/master:base/task/job_perftest.cc;l=30?q=job_perftest&ss=chromium Change-Id: Ie1ba432808f07498f90ab4c0af419b8f9b72e342 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2405799 Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#69854}
-
Jakob Kummerow authored
Bug: v8:7748 Change-Id: I463c7472ebaa5b4092b7f0e69e259abbf9c3bc06 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2390769 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/master@{#69853}
-
Georg Neis authored
... by unparking the local heap before accessing the handles. Bug: v8:7790 Change-Id: I0910fd8ad2a1e9cbbf312acb4f26358a09891f0f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2404455Reviewed-by:
Santiago Aboy Solanes <solanes@chromium.org> Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Auto-Submit: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#69852}
-
Victor Gomes authored
Only for the interpreter. Change-Id: I2456a7d6b385b3b8ebcb3ff8782ea5586289bea6 Bug: v8:10201 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2400343 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#69851}
-
Dominik Inführ authored
FLAG_local_heaps needs to be set before creating the context, otherwise the StressConcurrentAllocatorTask is already started. Setting the flag then races with background thread, which checks FLAG_local_heaps while creating LocalHeap. Bug: v8:10315 Change-Id: If6de748ec174dffb94a2582d24e37d24586ee95a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2404823Reviewed-by:
-
evih authored
Currently, the generic wrapper is used for i32 and i64 params and 0 or 1 i32 return value. Bug: v8:10701 Change-Id: I8c47e78fa9beeda01bdb647e1fcf9ebe6baf1ee4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2403243 Commit-Queue: Eva Herencsárová <evih@google.com> Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#69849}
-
Almothana Athamneh authored
NOTRY=true Bug: chromium:1126457 Change-Id: I5239fe552e71d7a9a20a07188a368fd57429142a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2404449 Commit-Queue: Almothana Athamneh <almuthanna@chromium.org> Reviewed-by:
-
Almothana Athamneh authored
Bug: chromium:1126467 Change-Id: Iae955b2fc832703f208e279c5bc4dff9c5b8e5cd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2400996Reviewed-by:
-
Leszek Swirski authored
This reverts commit 853efc77. Reason for revert: More TSAN failures: https://ci.chromium.org/p/v8/builders/ci/V8%20NumFuzz%20-%20TSAN/11176 Original change's description: > Reland "[offthread] Enable off-thread finalization in --future" > > This is a reland of ff0c5cfa > > Relanding after fixing TSAN failure in https://crrev.com/c/2404767. > > Original change's description: > > [offthread] Enable off-thread finalization in --future > > > > Enable the new LocalHeap-based off-thread finalization behind --future. > > > > Bug: chromium:1011762 > > Change-Id: I4b33fc300a34530d75aa1a3e197e0d1326994efa > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2403252 > > Commit-Queue: Leszek Swirski <leszeks@chromium.org> > > Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> > > Auto-Submit: Leszek Swirski <leszeks@chromium.org> > > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#69813} > > Bug: chromium:1011762 > Change-Id: I552a2668391707ee69162eb94143daa7c11721d6 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2404772 > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > Commit-Queue: Leszek Swirski <leszeks@chromium.org> > Cr-Commit-Position: refs/heads/master@{#69841} TBR=ulan@chromium.org,leszeks@chromium.org,verwaest@chromium.org,dinfuehr@chromium.org Change-Id: I291c16272a3fd02ee3afa23e2af7e66bae82a92e No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:1011762 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2404824Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/master@{#69846}
-
Mythri A authored
We used to store MinimorphicPropertyAccessInfo indexed on the feedback slot id. This works fine when there is no inlining but returns the wrong access information when functions are inlined. Index it based on FeedbackSource to avoid these problems. Bug: v8:10582,chromium:1125871 Change-Id: Id01010f3153f7e21495d73899a8604a64417ae95 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2401426 Commit-Queue: Mythri Alle <mythria@chromium.org> Reviewed-by:
-
Frank Tang authored
Bug: v8:10880 Change-Id: I7a9ba96e4b0c83565c4749101082c661e21d5ef1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2400598Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Frank Tang <ftang@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#69844}
-
Santiago Aboy Solanes authored
Since the AllowHandleDereference scope doesn't happen for kNeverSerialized (see https://crrev.com/c/v8/v8/+/2402033), there is no need to have the extra if. Bug: v8:7790 Change-Id: I4c9f93d2e754625e7b30aee61e2b502161bd60c6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2404770 Commit-Queue: Georg Neis <neis@chromium.org> Auto-Submit: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by:
-
Victor Gomes authored
This optimization does not work when the stack arguments are reversed. Change-Id: Ib543e6ca234cc70708909e0b3cd474b1309ec40e Bug: chromium:1126769, v8:10201 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2404775 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Auto-Submit: Victor Gomes <victorgomes@chromium.org> Reviewed-by:
-
Leszek Swirski authored
This is a reland of ff0c5cfa Relanding after fixing TSAN failure in https://crrev.com/c/2404767. Original change's description: > [offthread] Enable off-thread finalization in --future > > Enable the new LocalHeap-based off-thread finalization behind --future. > > Bug: chromium:1011762 > Change-Id: I4b33fc300a34530d75aa1a3e197e0d1326994efa > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2403252 > Commit-Queue: Leszek Swirski <leszeks@chromium.org> > Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> > Auto-Submit: Leszek Swirski <leszeks@chromium.org> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#69813} Bug: chromium:1011762 Change-Id: I552a2668391707ee69162eb94143daa7c11721d6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2404772Reviewed-by:
Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/master@{#69841}
-
Dominik Inführ authored
The problem here was that IncrementalMarking::Step was invoking new_space()->ResetOriginalTop() which sets original_top to the current top. IncrementalMarking::Step could be invoked during InvokeAllocationObservers(), which is called right after acquiring a new LAB and allocating the first object in it. However this first allocation might be from generated code with allocation folding enabled. The generated code might not use all of the memory it allocated and in that process move top backwards again. Nevertheless InvokeAllocationObservers() could already set original_top to the current top. If the generated code later not uses all of that memory, original_top can be bigger than top. Fix this problem by ensuring that original_top always equals the LAB start. Each time LAB start is moved/accounted for, original_top is now updated as well for the new space. Also IncrementalMarking::Step() isn't allowed to move original_top anymore. Bug: chromium:1116278, v8:10315 Change-Id: Ib18a0b07e2665b8ba933555387b84329cbecdf5b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2398519Reviewed-by:
-
Daniel Bevenius authored
The commit updates the way the usage is printed for cctest to make use of HelpOptions which allows the usage string to be passed into SetFlagsFromCommandLine function. Change-Id: I8dcd48ca8bb7b025f77c0f05ab37ce4f7b6fae04 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2402032Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#69839}
-
Leszek Swirski authored
When creating and inserting strings into the string table, we have to make sure that the writes to the string's fields (including its characters) are not reordered to after the write of the string into the table itself. Thanks TSAN! Bug: chromium:1011762 Change-Id: Ib8a22e3980f6b5c57561ca23549c1462c4c017c8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2404767 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Georg Neis authored
- serializer-*: In some stress configuration, the new map of x was GC'd at the beginning of optimization, thus generating a soft-deopt for the store to x (thus in turn skipping inlining of f). - native-context-*: In some stress configuration, f had its feedback flushed. Bug: v8:10892 Change-Id: Icd9f9c0ba6feb938ae8c3b0031b02b766f2e3f91 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2404764 Commit-Queue: Georg Neis <neis@chromium.org> Commit-Queue: Mythri Alle <mythria@chromium.org> Reviewed-by:
Mythri Alle <mythria@chromium.org> Auto-Submit: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#69837}
-
Georg Neis authored
Change-Id: Idb5ac9b0d3703e94f33d74318080790d00c4ec45 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2401428 Auto-Submit: Georg Neis <neis@chromium.org> Commit-Queue: Nico Hartmann <nicohartmann@chromium.org> Reviewed-by:
Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/heads/master@{#69836}
-
Santiago Aboy Solanes authored
Bug: v8:7790 Change-Id: Ib0c95f27d21e4aea09dcc9804a800b16440a2fe2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2403254Reviewed-by:
-
Santiago Aboy Solanes authored
Bug: v8:7790 Change-Id: I0e58244a679d5fd7f597c90c6f41ac255024de3a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2403253Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/471a6cd..b3e63d3 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/70f34e0..13bf125 Rolling v8/third_party/zlib: https://chromium.googlesource.com/chromium/src/third_party/zlib/+log/898c6c0..f8517bd TBR=machenbach@chromium.org,tmrts@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I42f50f1bd40a05adb6205a94e3d3007a4fc6b5f1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2405315Reviewed-by:
-
Ng Zhi An authored
Fix lowering of functions that returns the result of an i8x16 or i16x8 operation. Bug: v8:10507 Change-Id: Ia3b29e69cff7771f85dc5160937cbaf2bbc12b55 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2399049 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by:
-
Ng Zhi An authored
Since we are converting Int64x2 to Int32x4, we should be truncating the nodes, not sign-extending. Bug: v8:10507 Change-Id: I09dabdcaaa378842ffb4da5505199c188b5101f1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2404751Reviewed-by:
-
Zhao Jiazhong authored
Port 360c9294 https://chromium-review.googlesource.com/c/v8/v8/+/2355189 And support storing kS128 value in liftoff. Change-Id: I4429088bf6205aa24bfa61c2e4dbaf7bdab79132 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2402431Reviewed-by:
Zhi An Ng <zhin@chromium.org> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/master@{#69830}
-
- 10 Sep, 2020 6 commits
-
-
Omer Katz authored
This is a reland of f25cb50a Removed the problematic tests. The problem with the test was that we try to pop from an empty segment. GCC flags that as accessing beyond the array (i.e. index is uint16_t equivalent of -1). Preceding the actual pop is a DCHECK that asserts the segment isn't empty. In practice, since we have the DCHECK and access to the segment is always via a Local, this shouldn't be a problem. Unfortunately, GCC flags the access regardless. The DCHECK goes through a function pointer so GCC cannot determine that in our unittest the DCHECK would crash if index is 0 and the access would not happen (The indirection was added to allow for test DCHECK handlers that don't crash, so we can't mark the function pointer as noreturn). Drive-by: Segment::Pop and Segment::Push rely on the their Local counterparts checking of emptiness/fullness, so we should always access segments via Locals. Making the Segment ctor private. Original change's description: > Reland "cppgc, heap: Don't eagerly allocate worklist segments" > > This is a reland of c99147c6 > > Original change's description: > > cppgc, heap: Don't eagerly allocate worklist segments > > > > Bug: chromium:1056170 > > Change-Id: I75a6b5f52bfe8dd71abc086e5d1e060759ad7fc0 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2391254 > > Commit-Queue: Omer Katz <omerkatz@chromium.org> > > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#69778} > > Bug: chromium:1056170 > Change-Id: I4633da065976a6b2710d2f23b946fd2af0e65c83 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2401425 > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Commit-Queue: Omer Katz <omerkatz@chromium.org> > Cr-Commit-Position: refs/heads/master@{#69806} Bug: chromium:1056170 Change-Id: I7a122d1a2d20cd4e7c824d249975b4d3df30e03e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2403251Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Omer Katz <omerkatz@chromium.org> Cr-Commit-Position: refs/heads/master@{#69829}
-
Almothana Athamneh authored
Bug: chromium:1126469 Change-Id: Ia05590ef2e727ce3ac810610f579f6446682e8fa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2403242Reviewed-by:
-
Ng Zhi An authored
Add a bunch of lowering for I64x2 operations. This allows us to enable most of the I64x2 tests in test-run-wasm-simd.cc. Most of these lowering are straightforward. The load splat and load extends need an additional operation to convert the loaded Word32 nodes to Word64. Bug: v8:10507 Change-Id: I6c948918c03904d2b6778223a95bb2e34b692a5e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2401954Reviewed-by:
-
Dominik Inführ authored
Tests failed from time-to-time with --stress-concurrent-allocation. So run those tests with that flag disabled. Bug: v8:10315 Change-Id: I8a2b9f03d7bcd8a797134510f608dffb78dd1cdf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2403257Reviewed-by:
-
Camillo Bruni authored
Factor out common loop for copying MutableHeapNumbers in newly copied objects. Bug: v8:10763 Change-Id: I6cf2fc52c9ac72253dceaba518deacfde9905a9c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2402035 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Victor Gomes <victorgomes@chromium.org> Cr-Commit-Position: refs/heads/master@{#69825}
-
Seth Brenith authored
This reverts commit abb7cdc9. Reason for revert: regressions in jetstream2/gaussian-blur_sum Original change's description: > [regalloc] Loop-top values can be backedges too > > When counting which backedges conflict with a loop-top phi value, we > should include values introduced at the start of the loop. > > I don't expect this change to make performance differences on its own, > but it is a step toward changing the heuristic so that we're less likely > to introduce unnecessary load/store pairs across the backedge. > > Bug: v8:10606 > Change-Id: I299e388b0b964573119ba0b775d50f398c467c46 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2385715 > Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> > Commit-Queue: Seth Brenith <seth.brenith@microsoft.com> > Cr-Commit-Position: refs/heads/master@{#69752} TBR=sigurds@chromium.org,yolanda.chen@intel.com,seth.brenith@microsoft.com,thibaudm@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: v8:10606, chromium:1126663 Change-Id: Idde0b7c89f2376ae016e834fa37c38f3d9eb5c1e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2404020Reviewed-by:
Seth Brenith <seth.brenith@microsoft.com> Commit-Queue: Seth Brenith <seth.brenith@microsoft.com> Cr-Commit-Position: refs/heads/master@{#69824}
-
