- 11 Jun, 2021 11 commits
-
-
Thibaud Michaud authored
A try block may have no handler. Relevant links: https://github.com/WebAssembly/exception-handling/issues/131 https://github.com/WebAssembly/exception-handling/pull/157 R=clemensb@chromium.org Bug: v8:8091 Change-Id: Ia429762714dd87ed6b043f95c3496c65aaa8495f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2949100 Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Reviewed-by:
Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#75100}
-
Vicky Kontoura authored
This CL fixes WebSnapshotDeserializer::DeserializeContexts(), so that the new FunctionContext is allocated after the ScopeInfo is set up. Bug: v8:11525, v8:11706 Change-Id: Idb14c0fa5b5d51827e9f208f54c82a94535343a4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2953292 Commit-Queue: Vicky Kontoura <vkont@google.com> Reviewed-by:
Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/master@{#75099}
-
Georg Neis authored
Bug: v8:9974 Change-Id: I5853177be27d0d31087e436f0311d5a077cc2124 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2951723Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#75098}
-
Dominik Inführ authored
We do not need to park/unpark when we can acquire the lock without blocking. Bug: v8:10315, chromium:1218318 Change-Id: I7909936531ffe83087182d50e759113a9305fbcf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2953287 Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#75097}
-
Clemens Backes authored
Functions defined inside a class declarations are inline by default. Thus remove the 'inline' annotation from all such definitions. Drive-by: Move the 'inline' annotation of {WasmFunctionBuilder::signature} from the definition to the declaration. R=jkummerow@chromium.org Bug: v8:11384 Change-Id: I18be0b7d83c2414b3237e2f834e470c613143d7f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2953320Reviewed-by:Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#75096}
-
Leszek Swirski authored
Use the Streams API for file Blobs, instead of FileReader, to allow large files to be loaded in chunks. Change-Id: I241e0daff3f9c3d491dde2f3e8e52ea2236f05be Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2953286 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/master@{#75095}
-
Sigurd Schneider authored
We previously enumberated properties and then restricted them to real named properties. This CL changes it to only enumerate own properties in the first place. Bug: chromium:1213393 Change-Id: I8665a19a9beccae3bef99106924b65fb219d48ca Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2953284Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#75094}
-
Liu Yu authored
Bug: v8:11421 Change-Id: I1d3f8d3211d06d3e47ffd530715c1dbfbaf79fe8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2954905 Auto-Submit: Liu yu <liuyu@loongson.cn> Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/master@{#75093}
-
Georg Neis authored
The output was utterly confusing because block identities were printed in different ways: - "id:5" for a block with id 5 - "B5" for a block with rpo number 5 - also (!!!) "B5" for a block with id 5 With this CL, the last case above is eliminated such that there is no ambiguity. I originally wanted to unify the prefix syntax as well (e.g. "id:5" and "rpo:5"), but the prefixes are hard-coded in countless places including CodeGenerator, Turbolizer, and Verifier. Many of these are format strings that are painful to write more generically. Change-Id: I0eb70731c7b1ef9a9999e0bcb58b673288932e93 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2940890 Commit-Queue: Georg Neis <neis@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#75092}
-
Michael Achenbach authored
Bug: v8:9871 Change-Id: I66976c3490ec9fd732f99a8500bae9925bb89446 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2953185 Auto-Submit: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Liviu Rau <liviurau@chromium.org> Reviewed-by:
Liviu Rau <liviurau@chromium.org> Cr-Commit-Position: refs/heads/master@{#75091}
-
Fanchen Kong authored
This failure comes as the feedback is cleared but the CallFeedbackContent field remain unchanged. Bug: v8:11851 Change-Id: I75a0acad74dcaab1feafe97779e03caa8b7833de Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2948426 Commit-Queue: Fanchen Kong <fanchen.kong@intel.com> Reviewed-by:
Georg Neis <neis@chromium.org> Reviewed-by:
-
- 10 Jun, 2021 27 commits
-
-
Frank Tang authored
Stage 3 proposal Spec: https://tc39.es/intl-displaynames-v2/ R2T: https://groups.google.com/a/chromium.org/g/blink-dev/c/XOJE7zVlxnI/m/cnkuazxHAwAJ Design Doc: https://docs.google.com/document/d/17hQz4nOC7PJYhxc_MU-BRoT6BnYGZv66XlU1iGX0ywQ Bug: v8:11637 Change-Id: I6183f53bd7c3eae174c306debf0779a5be051d29 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2952040Reviewed-by:
Shu-yu Guo <syg@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#75089}
-
Andreas Haas authored
There was already a lookahead implementation in Liftoff for the case where a comparison was followed by kExprBrIf. This CL extends this lookahead implementation to kExprIf as well. This extension reduces the size of the code generated by Liftoff in the Epic benchmark by 1.5%. R=clemensb@chromium.org Bug: v8:11873, v8:11862 Change-Id: If4428bdd64eedcdd6dc543efc3b9945cbd8be3cc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2953322Reviewed-by:
-
Junliang Yan authored
Change-Id: I8b17676bbd9f614271f414a3a1432d0db0994adf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2953044 Commit-Queue: Junliang Yan <junyan@redhat.com> Commit-Queue: Milad Fa <mfarazma@redhat.com> Auto-Submit: Junliang Yan <junyan@redhat.com> Reviewed-by:
Milad Fa <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/master@{#75087}
-
Clemens Backes authored
This test is nondeterministic because it uses a SAB to synchronize between workers. Workers still execute in their own thread (with their own isolate) in predictable mode. Thus timing, and hence allocations, are unpredictable in both isolates. R=zhin@chromium.org Bug: v8:11746 Change-Id: Ic6b213f7e4062b2146e2b203c724bfc705b6e68d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2953323Reviewed-by:
Zhi An Ng <zhin@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#75086}
-
Manos Koukoutos authored
Changes: - Remove endianness transformations from WasmValue contstructors. WasmValue will now use the system's endianness. Remove CopyToWithSystemEndianness. - Remove endianness transformation from global variable load/stores in: wasm-compiler.cc, liftoff-compiler.cc, wasm-objects{.cc, -inl.h}, and wasm-interpreter.cc - Adjust SIMD tests that directly access part of a value by changing which lane they access within that value. We do that by introducing a LANE macro and use it over ReadLittleEndianValue. Change-Id: I99e97c6eae72e9a135b184633ec266049803bb03 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2944437 Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Reviewed-by: -
Camillo Bruni authored
Traverse the sampled stack in the correct order. This results in several order of magnitudes fewer flames rects. - Fix flame rendering by having a fixed-width border - Speed up flame rendering by setting shape-rendering to optimizeSpeed - Fix rendering empty timelines Bug: v8:10644, v8:11835 Change-Id: I5195d4d16a15c927ab25c7c111db69eeb0b0641a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2951728 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Patrick Thier <pthier@chromium.org> Cr-Commit-Position: refs/heads/master@{#75084}
-
Junliang Yan authored
Change-Id: Ide62ce4c8ac13e6ae8e417bbe06a28c3772be785 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2953040Reviewed-by:
-
Jakob Kummerow authored
With the upcoming "exception handling" proposal, we have to ensure that traps are not catchable. This patch adds missing "uncatchable" annotations to traps in the C-API and table-related instructions. Fixed: v8:11813 Change-Id: I7bbd5043ede58a5315bd5117eb496ed014e79e91 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2953160 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
-
Michael Lippautz authored
- Fix an issue where weak containers would not be marked properly when running with full object names. The problem was that in this configuration the object graph was not traversed at all in the first phase, meaning that no weak links would be found. - Add edges to weak containers in the second phase that actually builds the snapshot. - Mark all weak containers instead of just ephemerons, to avoid having fully weak containers show up as retainers. Bug: chromium:1056170 Change-Id: I8b29e00a5d77028892c16e3c29258cd598083082 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2951730 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/master@{#75081}
-
Michael Lippautz authored
JS nodes that are connected to C++ nodes are merged with them in the snapshot. Bug: chromium:1056170 Change-Id: I137a21b3d847e669bf65962224050f5402bcff7c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2951732Reviewed-by:
-
Patrick Thier authored
Explicitliy add --no-always-opt to prevent Fuzzer failures. Bug: v8:11853 Change-Id: Idf1ee842fd7e404516e27d1f5f5e6afe87fc5bd1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2951726Reviewed-by:
Victor Gomes <victorgomes@chromium.org> Commit-Queue: Patrick Thier <pthier@chromium.org> Cr-Commit-Position: refs/heads/master@{#75079}
-
Liu Yu authored
This is a reland of febfbb21 Original change's description: > [sparkplug] Adjust compare and jump function in sparkplug > > Mips and risc-v do not have the flag register and can not decide > whether to jump through flags in JumpIf(); > > Therefor, we merge the comparison with the jump; > > Bug: v8:11803 > > Change-Id: If53752da93b97e8ff65affdfe99e5de8e1a1493f > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2921034 > Auto-Submit: Liu yu <liuyu@loongson.cn> > Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Cr-Commit-Position: refs/heads/master@{#75001} Bug: v8:11803 Change-Id: Ib3cb89d8a9f59aad3fbd857881699e84e8fcd8aa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2945538 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Santiago Aboy Solanes authored
We have to not have any instructions between EmitOOLTrapIfNeeded and the movs. For this reason, we are now emitting EmitTSANStoreOOLIfNeeded after the store rather than before. We are also now requiring the code_kind to know if we are compiling a FOR_TESTING function. Finally, we have to differentiate between two different wasm-to-js functions: one lives in the wasm code space, and another one lives on the heap. The one that lives in wasm code space calls wasm stub calls, and the other one calls the builtin like JS does. Bug: v8:7790, v8:11600 Change-Id: Iafb4643068ae4e31881662e032f73af98a66baca Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2945185 Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Milad Fa authored
We can detect the sequence during instruction selection and if possible emit a single load/store byte reversed opcode instead of doing the same separately (i.e load/store and then reverse). Change-Id: Ib7d0c8c7105382637c33cafac5b5f4e23e8e553d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2950243Reviewed-by:
Junliang Yan <junyan@redhat.com> Commit-Queue: Milad Fa <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/master@{#75076}
-
Camillo Bruni authored
Migrate the remaining architectures to the new callee save RecordWrite approach. Bug: v8:11420 Change-Id: I9da56cbb5bf8c6ca4bcc7c0e2a1233e2f5ef587c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2944844 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Santiago Aboy Solanes <solanes@chromium.org> Cr-Commit-Position: refs/heads/master@{#75075}
-
Camillo Bruni authored
- Vertically adjust flamechart to show deep stacks - Highlight currently hovered function in the complete flamechart Bug: v8:10644, v8:11835 Change-Id: Ibb5839c332f28c552162943f3eb65435de11a36a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2950244Reviewed-by:
-
Lu Yahan authored
If a label was binded after Branch in 4096 offst, we should use Branchshort. Change-Id: I2197e2a18a43627370ed9b67b7ef7d678a2a62a8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2944795 Auto-Submit: Yahan Lu <yahan@iscas.ac.cn> Commit-Queue: Brice Dobry <brice.dobry@futurewei.com> Reviewed-by:
Brice Dobry <brice.dobry@futurewei.com> Cr-Commit-Position: refs/heads/master@{#75073}
-
Lu Yahan authored
In trampoline, we emit auipc+jalr first. But the offset between target and trampoline is less than int21, so we can use jal to replace auipc+jalr. It can reduce number of execution instruction. Change-Id: Idc37d80341030130c478209681cb54c63d1ddf27 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2939442 Auto-Submit: Yahan Lu <yahan@iscas.ac.cn> Commit-Queue: Brice Dobry <brice.dobry@futurewei.com> Reviewed-by:
-
Milad Fa authored
Batch compilation needs to remain disabled on unsupported platforms to avoid this compilation error: error: assignment of read-only location '* conclusion_pointer' Bug: v8:11790, v8:11420 Change-Id: I64aaf6476fdb585f8210331f31b01ebefe9c61c0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2949969Reviewed-by:
-
John Xu authored
For Cobalt's purpose in the past, we introduced base::Memcpy to intercept memcpy calls and replace it with SbMemoryCopy on Starboard/Cobalt. Recently Cobalt removed SbMemoryCopy because we found out that memcpy implementation is universal. To reduce the cost to maintain base::Memcpy, let us remove it and revert back to raw memcpy. Bug: v8:10927 Change-Id: I060f191f8f1aed8b78ffe4558a3743f3a2da008b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2951462Reviewed-by:
-
Marja Hölttä authored
This allows forward references among objects as well as contexts referencing objects. Bug: v8:11525 Change-Id: I45fd132344c5e0125d8287c668eac444fe1f8802 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2947408Reviewed-by:
-
Sathya Gunasekaran authored
This reverts commit 1f0b0ed0. Reason for revert: still crashing https://ci.chromium.org/ui/p/chromium/builders/try/android-marshmallow-arm64-rel/877258/test-results Original change's description: > Reland "heap: Fix initial GC configuration for C++-only heaps" > > This is a reland of 7ef67b2e > > Manually checked that the CL was not the culprit breaking > media_blink_unittests --gtest_filter=WebMediaPlayerImplTest.MemDumpReporting > > Original change's description: > > heap: Fix initial GC configuration for C++-only heaps > > > > Heaps in V8 start with a large limit that is shrunk upon young > > generation GCs, based on some liveness estimate. This provides best > > throughput during startup while at the same time finding a reasonable > > first limit. > > > > For C++ (embedder memory) there is no estimate which is why it was > > piggy-backing on V8. This breaks in scenarios where no JS memory is > > allocated. > > > > In this fix we start a memory reducer after embedder memory has hit > > the activation threshold if no GC happened so far. As soon as a single > > Scavenger has happened, we leave it up to the JS estimate to figure > > out a limit. Memory reducing GCs will then find a regular limit based > > on the initial live size. > > > > Drive-by: Give embedders the same activiation threshold of 8MB as JS. > > > > Bug: chromium:1217076 > > Change-Id: I8469696002ac2af8d75d6b47def062d2608387a1 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2944935 > > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > > Commit-Queue: Michael Lippautz <mlippautz@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#75012} > > Bug: chromium:1217076 > Change-Id: I482d8525379e33095834d5b41be8bb49bdd8a5d4 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2949094 > Commit-Queue: Michael Lippautz <mlippautz@chromium.org> > Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> > Auto-Submit: Michael Lippautz <mlippautz@chromium.org> > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#75048} Bug: chromium:1217076 Change-Id: Ia409d7a3a22127af749cff5eb5db1ff508b969e4 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2951468 Auto-Submit: Sathya Gunasekaran <gsathya@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#75068}
-
Dylan Cutler authored
Bug: chromium:1097184 Change-Id: Ifa64885cb74ffe05ef56aca59150c89d8f11dd1d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2945276 Auto-Submit: Dylan Cutler <dylancutler@google.com> Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#75067}
-
Benedikt Meurer authored
This change addresses inconsistencies wrt. to stepping into generator functions and breaking on the implicit initial yield. The new behavior is the following: 1. Stepping into a generator function doesn't trigger "generator stepping", but rather pauses right before the initial yield (assuming there a no non-simple parameters in between). 2. When paused on the initial yield and stepping into or over, we also don't turn on "generator stepping" immediately, but rather return to the caller and only enter "generator stepping" on SuspendGenerator bytecodes that correspond to `yield`s or `await`s in the source code. This matches the stepping behavior of regular functions more closely and seems like a good compromise. Fixed: chromium:901814 Change-Id: Ifc6c174011df1afea183e2c6ec21de27d72b17a7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2949099 Commit-Queue: Yang Guo <yangguo@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: -
Jakob Gruber authored
.. when concurrent inlining is on. SerializeBackPointer SerializeForElementLoad SerializeRootMap For SerializeRootMap: Due to changed root map access timing, it is now possible to see an abandoned prototype map - added logic for that in RemoveImpossibleMaps. Bug: v8:7790 Change-Id: Icdb3fff12536bfdc84923e7cd40bad9978a2a401 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2948658 Auto-Submit: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Jakob Gruber authored
In fond memory of kPossiblyBackgroundSerialized, this CL adds a new subtype of kNeverSerialized called NeverEverSerialized. Such refs are never ever serialized, i.e. not even when concurrent inlining is disabled. The first Ref in this category is RegExpBoilerplateDescriptionRef. The intent is to gradually transition all kNeverSerialized refs to NeverEverSerialized and then remove NeverEverSerialized (making it the default behavior). Bug: v8:7790 Change-Id: I8741a94212426a773ec3dc20758a41cb89f13368 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2947415 Auto-Submit: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Daoming Qiu authored
It adjusts V8 page size for performance reasons. The main use case is improving Node.js performance. The design doc is at:https://docs.google.com/document/d/1CO8Q0YZKJ3QKFRTk-aoJzmSFsuI8ALYQLtsjqLzyi-0/edit?usp=sharing Change-Id: Ie037d405a7116ccd986131d22d417b86ccf6a899 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2860840Reviewed-by:
-
- 09 Jun, 2021 2 commits
-
-
Peter Kasting authored
Bug: chromium:1216696 Change-Id: I0918215c2e2b845bd7b39e06128d74382a467b05 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2950262 Commit-Queue: Peter Kasting <pkasting@chromium.org> Auto-Submit: Peter Kasting <pkasting@chromium.org> Reviewed-by:
Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/master@{#75062}
-
Manos Koukoutos authored
- Add support for packed types. - Emit arguments first in wasm-module-builder.cc. Bug: v8:7748 Change-Id: I358ca13db4332e026ee5850de6f629822bc92b04 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2948887Reviewed-by:
-
