- 07 Jun, 2022 18 commits
-
-
Georgia Kouveli authored
GCC doesn't accept 'lr' in inline assembly, specifically for the list of clobbered registers. Change all uses to 'x30', for consistency. Bug: v8:10026 Change-Id: I5654fee4ca398dfdd99c34d09fc5294d169a9bd8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3693701Reviewed-by:
Igor Sheludko <ishell@chromium.org> Commit-Queue: Georgia Kouveli <georgia.kouveli@arm.com> Cr-Commit-Position: refs/heads/main@{#80980}
-
Milad Fa authored
Port e50d19cb Original Commit Message: https://crrev.com/c/3471854 already disabled the RecordWrite builtin specifically for incremental marking. Since this didn't regress performance as expected, we can now remove those versions of the builtin. This will simplify the barrier implementation a bit, but is also required for the shared heap write barrier. Unlike the generational barrier, the shared heap barrier can't be elided for map values. R=dinfuehr@chromium.org, joransiu@ca.ibm.com, junyan@redhat.com, midawson@redhat.com BUG= LOG=N Change-Id: Ic1a31fad3faaafeab077590d71d6d998eaddcc6a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3691128Reviewed-by:
Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Milad Farazmand <mfarazma@redhat.com> Reviewed-by:
Junliang Yan <junyan@redhat.com> Cr-Commit-Position: refs/heads/main@{#80979}
-
Manos Koukoutos authored
This is required for a V8 DEPS roll: https://chromium-review.googlesource.com/c/v8/v8/+/3691119. Change-Id: I65371eb7fd23b9dd13802e77bd3c14afdd592641 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3688407Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/main@{#80978}
-
Nikolaos Papaspyrou authored
Mostly in comments, again, not much to be said... Bug: v8:12425 Change-Id: I6d6c70b4e4dba70ec6ac7574caecc77b65316050 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3693698Reviewed-by:
-
Seth Brenith authored
I noticed in a recent build that C++ files from cctest didn't start compiling until after several slow non-parallel tasks such as running mksnapshot and linking v8_for_testing. I don't see any reason that cctest sources should wait for those tasks, so in this change I propose adjusting the build dependencies for more parallelism. Change-Id: I2472117c8555ac397fa1232954c8b699d6429d38 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3690170Reviewed-by:
Nico Hartmann <nicohartmann@chromium.org> Commit-Queue: Seth Brenith <seth.brenith@microsoft.com> Cr-Commit-Position: refs/heads/main@{#80976}
-
Samuel Groß authored
When the sandbox cannot be initialized, it's either because there is not enough virtual address space available, or because there is not enough memory for the kernel data structures needed for the reservation (this typically happens on Windows 7/8 where reserving virtual memory is expensive). Both cases should be reported as OOMs, not CHECK failures. Bug: chromium:1325302 Change-Id: I17bde9bcd4fbd6e3d54075b8891287c8fb01c1d7 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/+/3688406 Auto-Submit: Samuel Groß <saelo@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
-
Liu Yu authored
Port commit e50d19cb Bug: v8:11708 Change-Id: Ia9a8cb9d8cd9e768fc056bc5555959e0aaeb3694 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3692435Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Auto-Submit: Liu Yu <liuyu@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/main@{#80974}
-
Manos Koukoutos authored
Most notable: - Suggest '--experimental-wasm-gc' for wasm-gc type definitions. - Remove unused/useless fields from WasmTypeInfo. - Put more wasm Turbofan optimizations behind '--wasm-opt'. Change-Id: Ia298a58c2cf03964472a1445460d12ae72a5b04d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3688404Reviewed-by:
Maya Lekova <mslekova@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/main@{#80973}
-
Milad Fa authored
Port: f149912f Drive-by: Defined EnqueueFunction under baseline-batch-compiler for platforms without spakrplug support, currently getting a link error when making a debug build. Bug: v8:12887 Change-Id: I4fc8584ef09ad024280f7e40554a5e73a207b64f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3688474Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#80972}
-
Liu Yu authored
Use doubleword load/store to swap values in FPSackSlots instead of word load/store. Besides, fix error in gap resolver. Change-Id: I57e9d577a6001bc970ce6b56b6f890eb3e4d196c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3688325 Auto-Submit: Liu Yu <liuyu@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Reviewed-by:
-
Manos Koukoutos authored
Drive-by: Make the code less verbose my returning the input node from SetInt32Type. Bug: v8:7748, chromium:1332385 Change-Id: I2fde9c2168af1365e305e7e8d894b03487e8a8d9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3687692Reviewed-by:
-
Patrick Thier authored
It is now considered best effort, that in-place internalizable strings are promoted into the shared old space instead of non-shared old space. This was previously an invariant, but it doesn't hold if the whole page containing the shared string is promoted instead of individual objects. In addition with conservative stack scanning individual objects won't be moved. Bug: v8:12007 Change-Id: I7474738b02b0c18080cb2e82268a02bf9b480c40 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3688512Reviewed-by:
Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/main@{#80969}
-
Dominik Inführ authored
This build flag was removed in https://crrev.com/c/3314864. Bug: v8:12470 Change-Id: I365a1914ff096d07ae41d8bf35150615a9c91736 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3676853 Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#80968}
-
Nico Hartmann authored
In typed-optimization, Turbofan optimized NumberFloor(NumberDivide(...)) patterns where both inputs are known to be of Unsigned32 type, but the replacement couldn't be typed consistently. This CL introduces a new operator Unsigned32Divide, which has the same semantics, but can be typed consistently and thus allows the simplified lowering verifier to validate the graph correctly. Bug: v8:12619 Change-Id: Iad77154d3d840c94edfd3ab91ffa37c840da0bc9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3644790 Commit-Queue: Nico Hartmann <nicohartmann@chromium.org> Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/main@{#80967}
-
Dominik Inführ authored
https://crrev.com/c/3471854 already disabled the RecordWrite builtin specifically for incremental marking. Since this didn't regress performance as expected, we can now remove those versions of the builtin. This will simplify the barrier implementation a bit, but is also required for the shared heap write barrier. Unlike the generational barrier, the shared heap barrier can't be elided for map values. Bug: v8:11708 Change-Id: I44bc6ee79006a5be8c1b593dee7fc30c3b9cfa85 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3683341Reviewed-by:
Simon Zünd <szuend@chromium.org> Reviewed-by:
Omer Katz <omerkatz@chromium.org> Cr-Commit-Position: refs/heads/main@{#80966}
-
Igor Sheludko authored
Bug: v8:12797 Change-Id: Ide50026c7dc35197876e66cc53a7936acb765aa9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3687735 Auto-Submit: Igor Sheludko <ishell@chromium.org> Reviewed-by:
-
Gabriel Charette authored
Mirrors a Chromium change @ https://chromium-review.googlesource.com/c/chromium/src/+/3680123 and a v8 change @ https://chromium-review.googlesource.com/c/v8/v8/+/3687370/ Bug: chromium:1330114 Change-Id: I61b1e34d54a496dda25936efbcd339fa35e64fb1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3686476 Commit-Queue: Hannes Payer <hpayer@chromium.org> Reviewed-by:
Hannes Payer <hpayer@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/main@{#80964}
-
Gabriel Charette authored
Mirrors a Chromium change @ https://chromium-review.googlesource.com/c/chromium/src/+/3680123 Bug: chromium:1330114 Change-Id: I6fdfd93264e669965245f5ba696fb5b605e417fe Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3687370 Auto-Submit: Gabriel Charette <gab@chromium.org> Reviewed-by:
-
- 06 Jun, 2022 12 commits
-
-
Luis Fernando Pardo Sixtos authored
Currently the Isolate is gotten off of the object that the operation is being performed on. Shared objects return the shared Isolate, which is incorrect as it shouldn't be used to run JS, nor does it have HandleScopes open. Plumb the executing Isolate through. Bug: v8:12547 Change-Id: I2f500cbb707b3ce2e8a78203df9920374c190d28 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3691967 Commit-Queue: Luis Fernando Pardo Sixtos <lpardosixtos@microsoft.com> Reviewed-by:
-
Shu-yu Guo authored
Not all V8 build configs support JS shared memory features. Trying to create a new shared Isolate on such a config DCHECKs at runtime. Make the shared Isolate test fixture conditionally initialize the shared Isolate. Users must explicitly check for support. Bug: v8:12547 Change-Id: I3df1ce7eb5ae9a3c136f88ea8f44c650cc0408ab Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3687565 Commit-Queue: Shu-yu Guo <syg@chromium.org> Reviewed-by:
Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/main@{#80961}
-
Frank Tang authored
Spec Text: https://tc39.es/proposal-temporal/#sec-temporal.zoneddatetime.prototype.add https://tc39.es/proposal-temporal/#sec-temporal.zoneddatetime.prototype.subtract Bug: v8:11544 Change-Id: If4e1f71a05a0d1e88829bf219d4f90bd7a343877 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3617392Reviewed-by:
-
Frank Tang authored
Also implement AO: CompareEpochNanoseconds Spec Text: https://tc39.es/proposal-temporal/#sec-temporal.instant.compare https://tc39.es/proposal-temporal/#sec-temporal.instant.prototype.equals Bug: v8:11544 Change-Id: I953a890250ff0bf29cd24e4638bf17ceb5f9bb2f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3382057 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
-
Frank Tang authored
Also add AOs: AddISODate, RegulateISODate Change the return type of GetISO8601Calendar from MaybeHandle to Handle since it will never throw exception. Spec Text: https://tc39.es/proposal-temporal/#sec-get-temporal.zoneddatetime.prototype.hoursinday https://tc39.es/proposal-temporal/#sec-temporal-addisodate https://tc39.es/proposal-temporal/#sec-temporal-regulateisodate Bug: v8:11544 Change-Id: Id0b59e2818a095ee9390de2302501888fd93ca2b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3564937 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
-
Frank Tang authored
Spec Text: https://tc39.es/proposal-temporal/#sec-temporal.plaintime.prototype.add https://tc39.es/proposal-temporal/#sec-temporal.plaintime.prototype.subtract Bug: v8:11544 Change-Id: I0d684eec9eebfd26eceb6bb4c360025a33bd4c3c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3617390Reviewed-by:
-
Frank Tang authored
Spec Text: https://tc39.es/proposal-temporal/#sec-temporal.plaindatetime.prototype.add https://tc39.es/proposal-temporal/#sec-temporal.plaindatetime.prototype.subtract Bug: v8:11544 Change-Id: Ib76b090a62a932931ab48cb5814ce1f1050fae10 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3617391Reviewed-by:
-
Frank Tang authored
Spec Text: https://tc39.es/proposal-temporal/#sec-temporal.plaindate.prototype.add https://tc39.es/proposal-temporal/#sec-temporal.plaindate.prototype.subtract Bug: v8:11544 Change-Id: Iacb4b9ba7d481005d14e2e4d42e2422133f5ab42 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3617389 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
-
Liu Yu authored
Related to commit 2b6cbda0 Bug: v8:5210, chromium:1269989, chromium:1313647 Change-Id: I0046bdb3fe76a3eaf45e773b1fab87b65476cc1b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3690457 Auto-Submit: Liu Yu <liuyu@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Reviewed-by:
-
Fanchen Kong authored
When a 8x16 shuffle matches a packed byte to dword zero extension, 1. input1 is S128Zero after canonicalization, 2. the indices {0,4,8,16} are consecutive value in the range [0-15] and other indices are in the range [16-31], the shuffle can be matched to packed byte to dword zero extend. These shuffles are commonly used in image processing. Change-Id: I14d1e35401dbc5ecd91f67c46ea9762628835d01 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3547667Reviewed-by:Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Fanchen Kong <fanchen.kong@intel.com> Cr-Commit-Position: refs/heads/main@{#80953}
-
Liu Yu authored
Port commit a52b44f0 Bug: v8:12908 Change-Id: Ifcafab2f29d416f39fa48082e86c3c3b72508bad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3690453 Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Auto-Submit: Liu Yu <liuyu@loongson.cn> Reviewed-by:
-
Lu Yahan authored
Port commit a52b44f0 Original Commit Message: Prototype the instruction on the interpreter, and Arm64. Details of instruction lowerings on all relevant architectures can be found at: https://github.com/WebAssembly/relaxed-simd/issues/52 Change-Id: Ie0415f5c6a543517aa488a36ea5e575c6612ec0e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3687424 Auto-Submit: Yahan Lu <yahan@iscas.ac.cn> Commit-Queue: ji qiu <qiuji@iscas.ac.cn> Reviewed-by:
ji qiu <qiuji@iscas.ac.cn> Cr-Commit-Position: refs/heads/main@{#80951}
-
- 05 Jun, 2022 1 commit
-
-
Anton Bikineev authored
The CL splits the Oilpan giga-cage in two 2GB reservations: one for normal pages and the other for large ones. The split enables fast page-header lookup (assuming most objects reside on normal pages), which is needed for: 1) the young generation project, where the remembered set will move to pages; 2) the shared-cage project, to find HeapBase* from page-headers. Bug: v8:12231, chromium:1029379 Change-Id: I4ae9e8a75a307ed0dff9a2ec4f1247b80e17ebd9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3688519 Auto-Submit: Anton Bikineev <bikineev@chromium.org> Reviewed-by:
-
- 04 Jun, 2022 1 commit
-
-
Igor Sheludko authored
Bug: v8:11111 Change-Id: I52caef43e7f2b3921ef34eeb50e41f1dedf90e32 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3689570 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#80949}
-
- 03 Jun, 2022 8 commits
-
-
Igor Sheludko authored
... when allocating Code objects from background thread. Bug: chromium:1329012, chromium:1330887 Change-Id: Ia2731ba463381c826d14591f4ba3b3fe15d15a0b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3688517 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
-
Clemens Backes authored
Using the constexpr {value()} accessor instead of the non-constexpr implicit conversion operator makes GCC recognize the method as inlinable again. Before, we got (shortened): heap/heap-allocator-inl.h:167:18: error: inlining failed in call to always_inline ‘HeapAllocator::AllocateRaw’: function not inlinable The issue was introduced by https://crrev.com/c/3683321. R=mlippautz@chromium.org Bug: v8:12887 Change-Id: I5879dc0afb23d1d5bb782bf9444703e9cba148f1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3688515Reviewed-by: -
Andrey Kosyakov authored
This was originally part of https://crrev.com/c/v8/v8/+/3662540, but got accidentally lost during revert and re-roll. Change-Id: I38097884e50f086e2a71319cf820c628ba736a8a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3687417 Commit-Queue: Andrey Kosyakov <caseq@chromium.org> Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/main@{#80946}
-
Jakob Kummerow authored
Calling memset directly is faster than std::fill for multi-byte element types. Change-Id: I83b997740146688f87b86901825e31d6644bc25b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3687700 Auto-Submit: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#80945}
-
Milad Fa authored
Port a52b44f0 Original Commit Message: Prototype the instruction on the interpreter, and Arm64. Details of instruction lowerings on all relevant architectures can be found at: https://github.com/WebAssembly/relaxed-simd/issues/52 R=irezvov@chromium.org, joransiu@ca.ibm.com, junyan@redhat.com, midawson@redhat.com BUG= LOG=N Change-Id: Ia42e3f7fcb77d5515ee20bb428902cc3ff033f69 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3688290 Commit-Queue: Milad Farazmand <mfarazma@redhat.com> Reviewed-by:
-
Clemens Backes authored
The {AddOutOfLineTrap} method shows up with several percent of runtime in performance profiles. The majority of that was spent copying entries when growing the underlying vector. Pre-reserving space in that vector removes most of that overhead. R=thibaudm@chromium.org Change-Id: I1befb75b070d4f803770c2afcc5c82ffb9bfb522 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3688511Reviewed-by:Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#80943}
-
Milad Fa authored
Applying the set of unittest changes from https://crrev.com/c/3678208 to BE. Change-Id: I02d0f2f388720e3acc35660042d5c2c76fa589e1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3687474Reviewed-by:
Manos Koukoutos <manoskouk@chromium.org> Commit-Queue: Milad Farazmand <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/main@{#80942}
-
Jakob Kummerow authored
Fixed: v8:12935 Change-Id: Ib4dfdc276e6a9f465666b068bdbe31776429f359 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3687699 Auto-Submit: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
-
