- 22 Sep, 2022 11 commits
-
-
Camillo authored
V8-side implementation for trusted types fromLiteral. Create a separate JSArray root map for template literal objects to clearly identify untampered template literals belonging to a given context. Given that template literals are frozen arrays with a 'raw' property, we don't expect additional polymorphism. Drive-by-fix: Avoid ValidateElements call in NewJSArrayWithElements. Bug: chromium:1271149 Change-Id: I327b0fd99a2db3b57d35efa9293ddf2f14e555ea Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3572044Reviewed-by:
Shu-yu Guo <syg@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Auto-Submit: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#83383}
-
Matthias Liedtke authored
This is an unmodified reland of commit 67106ff4 The issue causing the revert should be addressed by commit 8598d770 Original change's description: > [wasm-gc] JS interop: Do not wrap structs/arrays by default > > Bug: v8:7748 > Change-Id: I441fd294bc0f31c0396217bc55c27159abacdbd1 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905725 > Reviewed-by: Manos Koukoutos <manoskouk@chromium.org> > Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> > Auto-Submit: Matthias Liedtke <mliedtke@chromium.org> > Commit-Queue: Matthias Liedtke <mliedtke@chromium.org> > Cr-Commit-Position: refs/heads/main@{#83338} Bug: v8:7748 Change-Id: I3e6a0a33bed4dbc7dd7c311465b25de4f8184894 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3912763Reviewed-by:
Manos Koukoutos <manoskouk@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Matthias Liedtke <mliedtke@chromium.org> Cr-Commit-Position: refs/heads/main@{#83382}
-
Manos Koukoutos authored
Bug: v8:12783 Change-Id: I09dcdfcf244af830380ca734859a46dd489e3836 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3909808 Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/main@{#83381}
-
jameslahm authored
We set the JSArray's length to the elements's length before, which is wrong when the elements have the slack part. We could serialize the correct length and only the actual elements excluding the slack part for JSArray's elements. And we do the same thing for the objects to avoid serializing unnecessary elements. Bug: v8:13304 Change-Id: Ib68e06f409bfcab5c57fb5532e188aa0099d1140 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905061Reviewed-by:
Marja Hölttä <marja@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#83380}
-
Simon Zünd authored
We don't remove the code just yet in case we need to re-enable the feature. This could be in case we discover workflows not covered by the "Scope View" and the scopes we report on "Debugger.paused". R=kimanh@chromium.org Bug: chromium:1365858 Change-Id: I636cc861af932156944a3f6e0a149cce0f939329 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905185Reviewed-by:
Kim-Anh Tran <kimanh@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/main@{#83379}
-
Leszek Swirski authored
This reverts commit 2a7f86ed. Reason for revert: Blocking the roll (https://ci.chromium.org/ui/p/chromium/builders/try/mac-rel/b8802346196479466065/test-results?q=ExactID%3Aninja%3A%2F%2Fgin%3Agin_unittests%2FGinShellTest.HelloWorld+VHash%3A46648b293475ce2a&clean=) Original change's description: > Reland "[v8] Use |AllocateAtLeast| for resizing v8 zones." > > This is a reland of commit 4444874c > This fixes a failure on the UBSan bots caused by assuming |Realloc| is always in-place if the new size is <= the value of |malloc_usable_size|. > > Original change's description: > > [v8] Use |AllocateAtLeast| for resizing v8 zones. > > > > This is part of an ongoing effort to reduce fragmentation in Chrome. Partition alloc shows v8 zones are a large user of memory in Renderer processes, and that there is fragmentation from these allocations. This CL will reduce this fragmentation by allowing v8 to use all allocated memory for its zones. > > > > Bug: v8:13193, chromium:1238858 > > Change-Id: Ibeac8bdba9d0e7ff66b14a3dde10e7c87d3cf953 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3889361 > > Reviewed-by: Adam Klein <adamk@chromium.org> > > Commit-Queue: Thiabaud Engelbrecht <thiabaud@google.com> > > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#83235} > > Bug: v8:13193, chromium:1238858 > Change-Id: I923bcbce8403dd7d84642340fd7202087b8a4440 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3910268 > Reviewed-by: Adam Klein <adamk@chromium.org> > Commit-Queue: Thiabaud Engelbrecht <thiabaud@google.com> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/main@{#83372} Bug: v8:13193, chromium:1238858 Change-Id: I32f9c4701a29c0516e3f587f1c6028e4d4158466 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3909358 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Owners-Override: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#83378}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/962a856..7f9e493 Rolling v8/buildtools: https://chromium.googlesource.com/chromium/src/buildtools/+log/dea2dd1..b79692f Rolling v8/buildtools/third_party/libc++/trunk: https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libcxx/+log/cec1dd0..a4dc7f1 Rolling v8/buildtools/third_party/libunwind/trunk: https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libunwind/+log/77b82eb..7ff728a Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/0a4b3b9..5b90d5e Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/0d126c9..08bb5c4 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/0cb9db1..082ae7e R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: Ifa490129d29a584ce272b0b5102c92dda2d1eeea Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3910281 Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Bot-Commit: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#83377}
-
Frank Tang authored
https://github.com/tc39/proposal-temporal/pull/2260 Spec text: https://tc39.es/proposal-temporal/#sec-temporal-getoffsetnanosecondsfor Bug: v8:11544 Change-Id: I107372ba883f97c1bf74b96cd0f592d47aa1f359 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3901199 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/main@{#83376}
-
Frank Tang authored
Changes in preparation for incorporating IETF draft https://github.com/tc39/proposal-temporal/pull/2385 The changes in this CL is needed to implement https://chromium-review.googlesource.com/c/v8/v8/+/3901196 and several other PR just agreed on TC39 Rename DateRecord => DateRecordWithCalendar Rename TimeRecord => TimeRecordWithCalendar Rename DateTimeRecord => DateTimeRecordWithCalendar Rename DateRecordCommon => DateRecord Rename TimeRecordCommon => TimeRecord Rename DateTimeRecordCommon => DateTimeRecord Bug: v8:11544 Change-Id: I77397363569c15320154fe0b226036f8d6df74a3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3893552Reviewed-by:
-
Liu Yu authored
Change-Id: I658c1b781163bcd3ca39bfceb74aef9d255247b8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3894795Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Commit-Queue: Liu Yu <liuyu@loongson.cn> Cr-Commit-Position: refs/heads/main@{#83374}
-
Shu-yu Guo authored
Blink has shipped import assertions since M91, so it is safe enough to go straight to shipping here. Bug: v8:10958 Change-Id: I3256172473a1ae8ce74e7fa63b14137e24568360 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3911378Reviewed-by:
-
- 21 Sep, 2022 26 commits
-
-
Thiabaud Engelbrecht authored
This is a reland of commit 4444874c This fixes a failure on the UBSan bots caused by assuming |Realloc| is always in-place if the new size is <= the value of |malloc_usable_size|. Original change's description: > [v8] Use |AllocateAtLeast| for resizing v8 zones. > > This is part of an ongoing effort to reduce fragmentation in Chrome. Partition alloc shows v8 zones are a large user of memory in Renderer processes, and that there is fragmentation from these allocations. This CL will reduce this fragmentation by allowing v8 to use all allocated memory for its zones. > > Bug: v8:13193, chromium:1238858 > Change-Id: Ibeac8bdba9d0e7ff66b14a3dde10e7c87d3cf953 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3889361 > Reviewed-by: Adam Klein <adamk@chromium.org> > Commit-Queue: Thiabaud Engelbrecht <thiabaud@google.com> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/main@{#83235} Bug: v8:13193, chromium:1238858 Change-Id: I923bcbce8403dd7d84642340fd7202087b8a4440 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3910268Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#83372}
-
Dominik Inführ authored
This CL implements collection of garbage in the shared spaces in the shared heap isolate. GC on such an isolate should now work correctly without worker isolates. Support for worker isolates will be implemented in a subsequent CL. Bug: v8:13267 Change-Id: I30125ce3b791e2faa0504d065f23639d6106e6b6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3904647Reviewed-by:
Jakob Linke <jgruber@chromium.org> Reviewed-by:
-
Shu-yu Guo authored
Bug: v8:12764 Change-Id: I1b48d4b685d0ce626da99ef5740edc1e1216ddc5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3907682Reviewed-by:
-
Michael Lippautz authored
Change-Id: Idc2a9019f5b0e67860edd8620a6cb0ed7002b1df Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3910029Reviewed-by:
Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Auto-Submit: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#83369}
-
Dominik Inführ authored
The string forwarding table invokes MakeThin even during a GC. However during a GC we didn't update the invalidated object size for OLD_TO_OLD because incremental marking was already stopped at that point. Change-Id: Ia2f0d2277b59b299c3c8bf5c3febbde634e3ec06 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3910028Reviewed-by:
Patrick Thier <pthier@chromium.org> Reviewed-by:
-
Michael Lippautz authored
- Use non-idle tasks to be able to process finalizers on time. - Only process finalizers while concurrent marking is still running. Bug: v8:13294 Change-Id: I1a2812c3fc350ea679c4c916c230cf736f2aa3ea Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3904648 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Anton Bikineev <bikineev@chromium.org> Cr-Commit-Position: refs/heads/main@{#83367}
-
Milad Fa authored
Change-Id: Ie5de6f4b7415c67eb77aa4b6e29764c595fca766 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905123Reviewed-by:
Junliang Yan <junyan@redhat.com> Commit-Queue: Milad Farazmand <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/main@{#83366}
-
Manos Koukoutos authored
- Add Turboshaft to the wasm pipeline (behind a flag). - Add a few operators. - Implement SimplifyLoopsPhase, which ensures each loop has at most two inputs. - Remove the unneeded effect argument from {FlagContinuation::FromTrap}. Bug: v8:12783 Change-Id: I03a3f8cf3af40fc75bf57cfbad973b754b13dd8c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3899126 Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Reviewed-by: -
Qifan Pan authored
Bug: v8:9407 Change-Id: Ie7993fcacc3e518da7b4af4c4ab20d8e4c47870c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905197Reviewed-by:
Nico Hartmann <nicohartmann@chromium.org> Commit-Queue: Qifan Pan <panq@google.com> Cr-Commit-Position: refs/heads/main@{#83364}
-
Manos Koukoutos authored
Bug: v8:11298, v8:13292 Change-Id: Ifabcbb64889012778439fb14e22a7cf885965b1e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905724 Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Reviewed-by:
-
Jakob Kummerow authored
There is no -0n, and we'd therefore never serialize such a BigInt. But we can't trust serialized data to not have gotten corrupted (or be fuzzer-generated), so guard against this case when deserializing. Fixed: chromium:1359937 Change-Id: If11d9a364480bae51911cc4a0ce8a719853139fe Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3904414Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
-
Camillo authored
Bug: chromium:1364974 Change-Id: Icfecc261cdb12fdd211cb821d48ae34a606b974e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905187Reviewed-by:
-
Omer Katz authored
Bug: v8:12612 Change-Id: Iae827f12611d5028e25d72a9270bcf86240b4f20 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3904413Reviewed-by:
-
Jakob Linke authored
This test breaks when interrupts occur with unfortunate timing. Maglev increases flakiness of this test since finished Maglev compiles all raise a new interrupt (and interrupts abort-and-retry regexp execution). Disable concurrent recompilation for this test, and drive-by fix the --trace-regexp-tier-up flag. Bug: v8:7700 Change-Id: I170c911fe2308b0b5ad9941e695f11f8925455f3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3904604Reviewed-by:
-
Darius M authored
Change-Id: I35d52bb53379023123a1c5cd25f8e7f6fe21a3f9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3906215Reviewed-by:
-
Liu Yu authored
Port commit 3f998527 Change-Id: Idbe8d53990b8c09e083f64774eecb146ecd2dc90 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905857 Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Auto-Submit: Liu Yu <liuyu@loongson.cn> Cr-Commit-Position: refs/heads/main@{#83357}
-
Leszek Swirski authored
... to avoid it being accessible from BG threads. Bug: v8:7700 Change-Id: I8fa7ac66016cb1f70925ed84a6552128d419f330 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3899128Reviewed-by:
-
Leszek Swirski authored
The DeepForEachInput helper was not incrementing the input_location index in the IsResultRegister case, while other paths (graph printing, code gen) were. Change these to consistently only increment the index when the input is used (i.e. match DeepForEachInput). Bug: v8:7700 Change-Id: Iaa54ef4e44db54023e3c19a088d14ad204bb2620 Fixed: chromium:1360800 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905722 Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Ting Chou authored
Correct the test expect result as the spec specifies the accumulator is 2*SEW bits. Fix the simulator implementation as well. R=qiuji@iscas.ac.cn Change-Id: Ia5d11b3214cf32635c3767df75992b2a50ee6980 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3878452 Commit-Queue: Yahan Lu <yahan@iscas.ac.cn> Reviewed-by:
Yahan Lu <yahan@iscas.ac.cn> Cr-Commit-Position: refs/heads/main@{#83354}
-
Ting Chou authored
Correct the arguments for std::fma() to double as the instruction expects both addend and destination are 2*SEW bits wide. Addressed corresponding implementation in the simulator as well. R=qiuji@iscas.ac.cn Change-Id: Ib3963a61c00ee9dc73af019574a1665de406cc32 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3878448 Commit-Queue: Yahan Lu <yahan@iscas.ac.cn> Reviewed-by:
-
Lu Yahan authored
Port commit 3f998527 Change-Id: Ic82f9d08fbc6c6df524e0361141c9a5d22e8924e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905856 Auto-Submit: Yahan Lu <yahan@iscas.ac.cn> Reviewed-by:
ji qiu <qiuji@iscas.ac.cn> Commit-Queue: ji qiu <qiuji@iscas.ac.cn> Cr-Commit-Position: refs/heads/main@{#83352}
-
Jakob Linke authored
.. and just the option for now, there's no logic behind this yet. --maglev-function-context-specialization enables FCS globally, and the MaglevCompilationInfo stores for each compilation job whether FCS is enabled. Bug: v8:7700 Change-Id: I4c32fe93fca70ae3644588902e282910a9673b74 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905382Reviewed-by:
-
jameslahm authored
... in Runtime_GrowArrayElements. Runtime_GrowArrayElements is only used when the elements kind is fast. And we could check the requested capacity according to the elements kind and throw error early. Bug: v8:13285 Change-Id: I68f59bc68995d622aac23be3e8daf05ac5fd5652 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905062 Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by:
-
Stephen Roettger authored
The last use was removed in this CLs: https://chromium-review.googlesource.com/c/v8/v8/+/3401585/ Bug: v8:12552, v8:13312 Change-Id: I72c639957ed3b1c2491eb43a54a54b8a96977b6f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905188Reviewed-by:
Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#83349}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/29d7990..962a856 Rolling v8/buildtools: https://chromium.googlesource.com/chromium/src/buildtools/+log/9e95466..dea2dd1 Rolling v8/buildtools/third_party/libc++/trunk: https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libcxx/+log/d128f2b..cec1dd0 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/fcf15b9..0a4b3b9 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/18bdadc..0d126c9 Rolling v8/third_party/fuchsia-sdk/sdk: version:9.20220919.1.1..version:9.20220919.2.1 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/70967a5..0cb9db1 R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: I34ee778225cc1a732e8bbfb69bbcab5fd08164bf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905132 Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Bot-Commit: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#83348}
-
Hao Xu authored
Only apply this optimization to the conditions that have multiple branch uses. Bug: v8:12484 Change-Id: Ieb74b8e879e62aa96344f2903f1fea6a1b769549 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3902559Reviewed-by:
-
- 20 Sep, 2022 3 commits
-
-
Junliang Yan authored
Change-Id: I23b2130798d28c479dfe6394ce6baf9503e74a1e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3904432 Commit-Queue: Junliang Yan <junyan@redhat.com> Reviewed-by:
-
Paolo Severini authored
Fixing an issue in WasmInstanceObject::GetGlobalBufferAndIndex. Bug: v8:13309 Change-Id: I52e65c109e43ce0300513604e71e587e1949f70a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3907666Reviewed-by:
Samuel Groß <saelo@chromium.org> Commit-Queue: Paolo Severini <paolosev@microsoft.com> Cr-Commit-Position: refs/heads/main@{#83345}
-
Frank Tang authored
1. Correct the return type of RoundTowardsZero to fix issue with double value > 2^64 2. In TemporalDurationToString: a. Use std::fmod instead of % to get the remainder b. Use extra xx_add variables to hold additional value which may overflow the double during computation. c. Use BigInt for days if the value is too large for double to ensure the precision. 3. Add tests with Number.MAX_SAFE_INTEGER and Number.MAX_VALUE in values for Duration toJSON in mjsunit Bug: v8:11544 Change-Id: Icac4f669ed1c591e947b51c82dd48bdef7a6db6e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3900813Reviewed-by:
-
