- 19 Aug, 2022 7 commits
-
-
Samuel Groß authored
The function is no longer used in Chromium or V8 and can therefore be deleted. This CL also simplifies V8::GetSandboxSizeInBytes, which now no longer needs to be able to deal with an uninitialized sandbox. Bug: v8:10391 Change-Id: I22d6b0e03de1fd2ba3d38c4e476fca44068b62f9 Cq-Include-Trybots: luci.v8.try:v8_linux64_heap_sandbox_dbg_ng,v8_linux_arm64_sim_heap_sandbox_dbg_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3769690Reviewed-by:
Igor Sheludko <ishell@chromium.org> Commit-Queue: Samuel Groß <saelo@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#82583}
-
Michael Lippautz authored
Bug: v8:13089 Change-Id: Ic1c5a596adb822494aff490e04bd23cf84fb53f6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3840295 Commit-Queue: Anton Bikineev <bikineev@chromium.org> Reviewed-by:
Anton Bikineev <bikineev@chromium.org> Auto-Submit: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#82582}
-
Dominik Inführ authored
This CL removes the COMPLETE state from incremental marking. Since then the only states left were STOPPED and MARKING, we can replace the state with an is_running_ boolean field. The state could change back-and-forth between MARKING and COMPLETE. IsMarking() was already also checking for COMPLETE. So most code already treated both states the same. IsComplete() now checks whether marking is running and a transitive closure was reached already. IncrementalMarking::Step() didn't process the marking queue when in COMPLETE. This should be relatively rare though since it only transitioned into COMPLETE when the stack guard was armed and the allocation observer ran again before reaching a stack guard check. Bug: v8:12775 Change-Id: Ied48d8c512ad3d1b3d2e29393d43b434b5fda8fe Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3835689Reviewed-by:
-
Nico Hartmann authored
This reverts commit c3a5c5b1. Reason for revert: https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux64%20-%20shared/21941/overview Original change's description: > [heap] Ensure all old-to-shared slots are recorded > > This CL adds verification of the old-to-shared remembered set to > --verify-heap. During shared GCs client heaps will be scanned for > references into the shared heap, this CL will CHECK that every found > slot is contained in the old-to-shared remembered set. After this > gets a bit more stable, the full heap iteration can be dropped and we > can fully rely on the remembered set instead. > > Bug: v8:11708 > Change-Id: I0b5c4edfe3271306e4e7af7394472534113e1953 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3792605 > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> > Cr-Commit-Position: refs/heads/main@{#82578} Bug: v8:11708 Change-Id: I26553d3b06d0e257a3425eeb884ccce57f026bde No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3841567 Owners-Override: Nico Hartmann <nicohartmann@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Nico Hartmann <nicohartmann@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#82580}
-
Qifan Pan authored
`JSWasmCallData` is replaced with a flag `do_conversion` to indicate if conversions of arguments and returns are needed, which is set as false for inlined js-to-wasm call wrappers. Bug: v8:9407 Change-Id: I35244c8fc13d464d48031fb9d7d04ab277646ec5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3837858Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Qifan Pan <panq@google.com> Reviewed-by:
Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/heads/main@{#82579}
-
Dominik Inführ authored
This CL adds verification of the old-to-shared remembered set to --verify-heap. During shared GCs client heaps will be scanned for references into the shared heap, this CL will CHECK that every found slot is contained in the old-to-shared remembered set. After this gets a bit more stable, the full heap iteration can be dropped and we can fully rely on the remembered set instead. Bug: v8:11708 Change-Id: I0b5c4edfe3271306e4e7af7394472534113e1953 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3792605Reviewed-by:
-
Lu Yahan authored
This is a reland of commit 776b9eb9 Original change's description: > [WATCHLISTS] Add riscv watch > > Change-Id: I6e4dc69d6f22d3108ae74552b72bcafc0be3db64 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3793476 > Commit-Queue: Yahan Lu <yahan@iscas.ac.cn> > Reviewed-by: Victor Gomes <victorgomes@chromium.org> > Cr-Commit-Position: refs/heads/main@{#82092} Change-Id: I33ff1808de80f03fdfd7c977b29a895c8110bae0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3835293Reviewed-by:
Victor Gomes <victorgomes@chromium.org> Commit-Queue: Yahan Lu <yahan@iscas.ac.cn> Cr-Commit-Position: refs/heads/main@{#82577}
-
- 18 Aug, 2022 28 commits
-
-
Frank Tang authored
Add a version of BalanceDuration which take two TimeDurationRecord and add them internally after converting to BigInt as nanoseconds so it will not overflow the double. Use "std::isinf()" instead of "!std::isfinite()" Inspired by https://github.com/tc39/proposal-temporal/issues/2380#issuecomment-1219194995 Bug: v8:11544 Change-Id: I29e06fa857ff43f2668e1e4ffd07735ff6efee42 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3837852 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/main@{#82576}
-
Stephen Belanger authored
This is a reland of commit 872b7faa Original change's description: > Fix Context PromiseHook behaviour with debugger enabled > > This is a solution for https://github.com/nodejs/node/issues/43148. > > Due to differences in behaviour between code with and without the debugger enabled, some promise lifecycle events were being missed and some extra ones were being added. This change resolves this and verifies the event sequence is consistent between code with and without the debugger. > > Change-Id: I3dabf1dceb14233226b1752083d659f1c2f97966 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3779922 > Reviewed-by: Victor Gomes <victorgomes@chromium.org> > Commit-Queue: Camillo Bruni <cbruni@chromium.org> > Reviewed-by: Camillo Bruni <cbruni@chromium.org> > Cr-Commit-Position: refs/heads/main@{#82132} Change-Id: Ifdd407261c793887fbd012d5a04ba36b3744c349 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3805979Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Clemens Backes <clemensb@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
-
Dominik Inführ authored
No need to insert into the old-to-shared remembered set for the shared isolate itself. Check whether the host object is in the shared isolate before inserting into the remembered set. Bug: v8:13208, v8:11708 Change-Id: Ic1442653f6c27c51444544cd7b31356594b712e1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3840298 Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by:
-
Frank Tang authored
Use SNPrintf to handle bigger unit duration fields. Spec Text: https://tc39.es/proposal-temporal/#sec-temporal-temporaldurationtostring Fix test: https://github.com/tc39/test262/blob/main/test/built-ins/Temporal/Duration/prototype/toString/precision-formatted-as-decimal-number.js Bug: v8:11544 Change-Id: I63a6e823652a0826216593cd153ef5103f94e7a9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3834437Reviewed-by:
-
Anton Bikineev authored
Pointer compression regresses binary size on Fuchsia by about 300K. However, the change improves Oilpan memory by 15-20% (2-4% of PMF), which is beneficial for memory-impoverished platforms. Bug: chromium:1325007 Fuchsia-Binary-Size: See commit description. Change-Id: Ie16fd992e45e29e264549a960e9755ec58da1691 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3829313Reviewed-by:
Wez <wez@chromium.org> Commit-Queue: Anton Bikineev <bikineev@chromium.org> Reviewed-by:
-
Deepti Gandluri authored
Reference instruction lowerings are in the corresponding issue: https://github.com/WebAssembly/relaxed-simd/issues/40 Lowers directly to Pmulhrsw in the macro assembler as we use DefineSameAsFirst in place of the Movdqa on non-AVX hardware Bug: v8:12609, v8:12284 Change-Id: I6de45a2d8895637f895d3b0cc68f5dd1f67f77aa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3837853Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Reviewed-by:
-
Frank Tang authored
Fix BalanceDuration to pass relativeTo to BalancePossiblyInfiniteDurationResult and then pass to NanosecondsToDays. The bug is introduced in https://chromium-review.googlesource.com/c/v8/v8/+/3781117 The spec text in 4-a of BalancePossiblyInfiniteDuration is "a. Let result be ? NanosecondsToDays(nanoseconds, relativeTo)." but the code wrote "a. Let result be ? NanosecondsToDays(nanoseconds, *undefined*)." Spec Text: https://tc39.es/proposal-temporal/#sec-temporal-balancepossiblyinfiniteduration Bug: v8:11544 Change-Id: I3ea9a3b71521cdcc210e9db370d6e849fcde56ee Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3834431 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
-
Frank Tang authored
Spec text: https://tc39.es/proposal-temporal/#sec-temporal-parsetemporaldurationstring Bug: v8:11544 Change-Id: I2d54759c07529f95c7a27c334ee5d3fa6760b2e0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3835292Reviewed-by:
-
Shu-yu Guo authored
AcqRel barriers are currently unused and will be used by the shared value barrier in a future CL. Bug: v8:12547 Change-Id: I8ae40b9e17f007441125dfa5d0a04f46565785fd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3827319Reviewed-by:
-
Milad Fa authored
mksnapshot is currently failing as FlagValues are not aligned to kMinimumOSPageSize. Change-Id: Ib6e88a3bd72af874022647ff9708024902f21a50 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3838773Reviewed-by:
Milad Farazmand <mfarazma@redhat.com> Reviewed-by:
-
Danylo Boiko authored
Bug: v8:7327 Change-Id: I7312ec4fb23bbf1c67fdf110de221105279bfa4a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3837859Reviewed-by:
-
Samuel Groß authored
This is a reland of commit 6ec7be21 The issues that caused the CL to be reverted appear to be unrelated to this change as they still occurred after the revert. Original change's description: > [sandbox] Sandboxify WasmExportedFunctionData::sig > > This CL changes the WasmExportedFunctionData class to store a direct > ExternalPointer to the wasm::FunctionSig instead of referencing it > through a Foreign. This in turn makes it possible to use a unique > pointer tag for that external pointer when the sandbox is enabled. > > Drive-by: move WasmInternalFunction::call_target external pointer to the > end of the object, in line with other external pointer fields. > > Bug: v8:10391, v8:12949 > Change-Id: Ic3ff622a075c9eaa2f8d8835803437466290c928 > Cq-Include-Trybots: luci.v8.try:v8_linux64_heap_sandbox_dbg_ng,v8_linux_arm64_sim_heap_sandbox_dbg_ng > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3829086 > Commit-Queue: Samuel Groß <saelo@chromium.org> > Reviewed-by: Igor Sheludko <ishell@chromium.org> > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> > Cr-Commit-Position: refs/heads/main@{#82523} Bug: v8:10391, v8:12949 Change-Id: I108810ce86b95289dfb6d6377535813deac79a9f Cq-Include-Trybots: luci.v8.try:v8_linux64_heap_sandbox_dbg_ng,v8_linux_arm64_sim_heap_sandbox_dbg_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3838109Reviewed-by:
-
Michael Lippautz authored
Bug: v8:13141 Change-Id: I05e905a40a572c7f85f60629b2303cd73ae06a70 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3838731 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/main@{#82564}
-
Feng Yu authored
Bug: v8:12781 Change-Id: I1bf06cd74b82e98f44e00f8d6e9049d1b92c86cb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3827121Reviewed-by:
-
Michael Lippautz authored
Provides a v8::base::Malloc::AllocateAtLeast() method that is also UBSan-safe and use it in the GC's worklist. Depends on https://crrev.com/c/3834601 Bug: v8:13193 Change-Id: I1bd182e613fb3c6a5a6b90bf56f12bd210d5ef8c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3833818 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
-
Camillo authored
- Force RecordError in case of a TerminationException - Remove Module::RecordErrorUsingPendingException - Use more raw objects and instance methods if possible Bug: v8:12379 Change-Id: Ia7e73715c3cdfe59d3fa324be3ce4213e454ff26 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3829087Reviewed-by:
Patrick Thier <pthier@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#82561}
-
Camillo authored
Add outlined StackLimitCheck::HandleInterrupt helper for the uncommon path. Change-Id: Ib13dc84ac632f3455d5933748428f9550a23d435 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3829088Reviewed-by:
Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/main@{#82560}
-
Michael Lippautz authored
Traced nodes were allocated black, even outside of GCs. Nodes would always survive one GC, while the objects pointed to could die. This CL removes black allocation and relies on proper write barriers (that are anyways in place) to mark the nodes and their objects. This also means that marked nodes should always point to live objects which is now verified in the atomic pause. Bug: v8:13141 Change-Id: Ie5cdc92d8fe5f57865d02b71d3fae9425ae532fa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3820070 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
-
Matthias Liedtke authored
Also fix eqref/i31ref fromJS() handling to accept unwrapped Smis. This does not convert HeapNumbers to Smis if they fit. Bug: v8:7748 Change-Id: Ida70a826f9541b7f3fbe9eecbb2b4fe362b5ef70 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3829477 Commit-Queue: Matthias Liedtke <mliedtke@chromium.org> Reviewed-by:
-
Samuel Groß authored
The previous code incorrectly rounded down the number of entries to free to kBlockSize (expressed in KB) instead of kEntriesPerBlock (expressed in # of entries) to compute the start of the evacuation area. Further, depending on the block sized used, the previous heuristics does not necessarily guarantee that at least one full block would be evacuated. This CL fixes both of these issues. Bug: v8:10391 Change-Id: I5ddecd5d582bcf89e1c52df431f006889685320a Cq-Include-Trybots: luci.v8.try:v8_linux64_heap_sandbox_dbg_ng,v8_linux_arm64_sim_heap_sandbox_dbg_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3837860Reviewed-by:
-
Tobias Tebbi authored
Bug: chromium:1353360 Change-Id: Id39bfb72ba0ffc6e547b907bb82599fb4a0529a5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3834255 Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Auto-Submit: Tobias Tebbi <tebbi@chromium.org> Reviewed-by:
-
Jose Dapena Paz authored
In existing implementation, of MethodLoad event, the method name passed to ETW is coming from CodeEventLogger::CodeCreateEvent, and includes the source file or URL, column and line numbers, method name and a marker for the kind of code generation. This is partially redundant, as the reference to source ID will point to the already generated SourceLoad event, with the file information. Also, Windows Performance Analyzer will already pick line and column number for the stack representation. So, for those cases, we just need to send to ETW the script method name. Even better, this changeset uses the DebugNameCStr logic to retrieve the inferred name in case there is no name available. Bug: v8:12987 Change-Id: If09c1fedc9da158a3c72932655e2e6b09e818d93 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3763862Reviewed-by:
-
V8 Autoroll authored
Change-Id: Ia8c534ccbec53fc2d59b6d357697513bfec3a015 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3837856Reviewed-by:
Lutz Vahl <vahl@chromium.org> Commit-Queue: Lutz Vahl <vahl@chromium.org> Cr-Commit-Position: refs/heads/main@{#82554}
-
JianxiaoLuIntel authored
`mksnapshot --trace_turbo` will crash because builtins have no bytecode. Bug: v8:7327 Change-Id: I61740b9ce934e85d158518787a2c7dc76c57e8d2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3834641Reviewed-by:
-
Dominik Inführ authored
Introducing IncrementalMarking::AdvanceForTesting as last bottleneck for driving incremental marking in addition to AdvanceFromTask and AdvanceOnAllocation. Now that we have those 3 bottlenecks, Step() and AdvanceWithDeadline() can become private methods in IncrementalMarking. We also don't need the StepResult return value in Step() anymore, which allows us to remove CombineStepResult. Bug: v8:12775 Change-Id: I702714439ef7ea4b9abf2156387503d4d00a7a48 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3823131Reviewed-by:
-
Matthias Liedtke authored
This is a reland of commit ee89a269 Original change's description: > [wasm-gc] Add extern.externalize > > This adds `extern.externalize(ref null any): ref null extern` to wasm > which packs wasm objects into JS objects if the js-interop flag is not set. > This is the counterpart to extern.internalize introduced in > 50ec8a11. > > Bug: v8:7748 > Change-Id: I67b8fe6d70b9f526ff6c43b0a4d7861c7ff5dad0 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3825879 > Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> > Commit-Queue: Matthias Liedtke <mliedtke@chromium.org> > Cr-Commit-Position: refs/heads/main@{#82492} Bug: v8:7748 Change-Id: Ie13cfd6464006dcadc2a53f2dbf77f76ab185504 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3829940Reviewed-by:
-
Peter Kasting authored
This fixes a compile error in C++20. Bug: chromium:1284275 Change-Id: If7f634f56bea94d594bd7a1e660b902dbebbab1b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3835291Reviewed-by:
-
Dominik Inführ authored
Maglev write barrier needs to use different page flag mask to also call into the slow path of the barrier for old-to-shared pointers. Bug: v8:11708 Change-Id: I9ff5ead0517e9682672452f9868b16fa0dd94be2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3834256Reviewed-by:
-
- 17 Aug, 2022 5 commits
-
-
Frank Tang authored
1. Add if/throw based on IsValidEpochNanoseconds() in DisambiguatePossibleInstants, ParseTemporalInstant, GetIANATimeZoneEpochValueAsArrayOfInstantForUTC, GetIANATimeZoneEpochValueAsArrayOfInstant, JSTemporalTimeZone::GetPossibleInstantsFor, and InterpretISODateTimeOffset( 2. Add assert IsValidEpochNanoseconds in GetISOPartsFromEpoch 3. Fix ISODateTimeWithinLimits These changes are syncing of the following PRs: https://github.com/tc39/proposal-temporal/pull/2277 https://github.com/tc39/proposal-temporal/pull/2084 https://github.com/tc39/proposal-temporal/pull/2312 https://github.com/tc39/proposal-temporal/pull/2273 https://github.com/tc39/proposal-temporal/pull/2117 Spec Text: https://tc39.es/proposal-temporal/#sec-temporal-disambiguatepossibleinstants https://tc39.es/proposal-temporal/#sec-temporal-parsetemporalinstant https://tc39.es/proposal-temporal/#sec-temporal.timezone.prototype.getpossibleinstantsfor https://tc39.es/proposal-temporal/#sec-temporal-interpretisodatetimeoffset https://tc39.es/proposal-temporal/#sec-temporal-getisopartsfromepoch https://tc39.es/proposal-temporal/#sec-temporal-isodatetimewithinlimits Bug: v8:11544 Change-Id: I38244d039f33e294b698d470b587b1b44b72fa09 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3831150Reviewed-by:
-
Frank Tang authored
Pass OrdinaryObjectCreate(*null*) to DifferenceISODateTime in NanosecondsToDays and to DifferenceZonedDateTime in AddDuration https://github.com/tc39/proposal-temporal/pull/2295 Bug: v8:11544 Change-Id: Ied1860b755b1cebd0fbcbc4bd574cd525f108378 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3835263Reviewed-by:
-
Frank Tang authored
Move calendar validation out of ParseTemporalCalendarString Spec PR https://github.com/tc39/proposal-temporal/pull/1954 Bug: v8:11544 Change-Id: I4dbfcba1a9f5940d5692547b7ea212ebe45ca341 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3835265Reviewed-by:
-
Frank Tang authored
See issues in https://github.com/tc39/test262/issues/3553 and https://github.com/tc39/proposal-temporal/issues/2165 Bug: v8:11544 Change-Id: Iefe6353e95178e1241a7f29c80b24baad2a8428d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3835266 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
-
Frank Tang authored
Pass undefined for option in calendar monthDayFromFields and yearMonthFromFields https://github.com/tc39/proposal-temporal/issues/1685 Bug: v8:11544 Change-Id: I3fd37e176bd83dc0b01d92a3c323d2933291c49b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3835262Reviewed-by:
-
