- 15 Nov, 2021 18 commits
-
-
Samuel Groß authored
This change allows clients of the RegionAllocator to provide callbacks that are invoked when regions are split or merged. This will later be needed on Windows when a RegionAllocator is used to manage a placeholder mapping as these need to be split and merged (using the VirtualFree API) as well. Bug: chromium:1218005 Change-Id: I228b41bdb43c4a9ef0db04de9b121dea6b5f12f9 Cq-Include-Trybots: luci.v8.try:v8_linux64_heap_sandbox_dbg_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3264287 Commit-Queue: Samuel Groß <saelo@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#77903}
-
Liu Yu authored
Port commit 3e3a027d Beside, some registers are changed to callee-saved, and the previous related save and restore operations are removed. Bug: v8:11382 Change-Id: Ic3161f8173771c1b7c190c77cbaf2534f52ec422 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3281673Reviewed-by: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Auto-Submit: Liu yu <liuyu@loongson.cn> Cr-Commit-Position: refs/heads/main@{#77902}
-
Dominik Inführ authored
Code pages need to be swept on the main thread for now. Originally this was done to prevent RWX on code pages, but there might be more other smaller issues like the linked bug. Most likely this restriction isn't a problem for concurrent SP at the moment, so stick with this invariant for now. Bug: chromium:1269558, v8:12054 Change-Id: Icf7a7ce9714b9ef07b1a5070f0b0dd963b6d3011 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3279682 Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#77901}
-
Dominik Inführ authored
This CL adds Heap::FreeLinearAllocationAreas to free all local allocation buffers (LABs). We use this to give up LABs for a local GC. The second method Heap::FreeSharedLinearAllocationAreas is used to free all LABs in the shared heap for shared GCs and in the future also on isolate shutdown. Bug: v8:10315 Change-Id: Ie5cbb68c95fae027055aeaf4458473b04b15b18c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3279681Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/main@{#77900}
-
Manos Koukoutos authored
The stored value might be an allocation that can be removed once the Store node is removed. We need to revisit this node manually because inputs in a node removed with ReplaceWithValue are not revisited automatically. Bug: v8:11510 Change-Id: I57cb8955a3e2f7143474ad7ced9d946e6d1cc18e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3277880Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/main@{#77899}
-
Camillo Bruni authored
We do have snapshot decompression trace events, let's also add a runtime call stats scope for easy comparison. Bug: chromium:1269494, chromium:1270039 Change-Id: If467cc38f37a0ea9d84e501b4984bf72736c8fa4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3279962 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Auto-Submit: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/main@{#77898}
-
Victor Gomes authored
This allow us to change the target to be built in V8 CI without changing the bot recipe. No-Try: true Bug: v8:12388 Change-Id: I5513e264e7fb5ee273961b88171da8fa793c24f8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3280223 Auto-Submit: Victor Gomes <victorgomes@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#77897}
-
Thad House authored
Extend bazel build to support windows in addition to linux and mac. Bug: v8:11234 Change-Id: I264f8dd8a33e221890a408d504a94ce2bc9cc19f No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3265064Reviewed-by: Victor Gomes <victorgomes@chromium.org> Commit-Queue: Victor Gomes <victorgomes@chromium.org> Cr-Commit-Position: refs/heads/main@{#77896}
-
Camillo Bruni authored
Bug: v8:11165 Change-Id: I4b5160245d032f3b57167344b03553e5c0374ca2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3275564Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#77895}
-
Leszek Swirski authored
Posting compile tasks from the parser has several issues: 1. We don't know how many functions there will be total, so we can't yet allocate shared_function_infos array on the Script 2. Without this array, inner function compiles can't look up their own inner functions during bytecode finalization, so we can't run that finalization before script parse completes 3. Scope analysis can't have run yet, so we can only post top-level function tasks and if we allocate SharedFunctionInfos early they are forced into a bit of a limbo state without an outer ScopeInfo. Instead, we can post compile tasks during bytecode generation. Then, the script parse is guaranteed to have completed, so we'll have a shared_function_infos array and we will have allocated ScopeInfos already. This also opens the door for posting tasks for compiling more inner functions than just top-level, as well as generating better code for functions/methods that reference same-script top-level let/const/class. Bug: chromium:1267680 Change-Id: Ie1a3a3c6f1b264c4ef28cd4763bfc6dc08f45d4d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3277884 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#77894}
-
Shu-yu Guo authored
Bug: v8:12382 Change-Id: I31a9e919db56cf7642b2f5e22352ce3ebe0f6e23 Cq-Include-Trybots: luci.v8.try:v8_linux64_single_generation_dbg_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3278675 Auto-Submit: Shu-yu Guo <syg@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#77893}
-
Johann authored
TestExpectations has been empty for almost 3 years and its use in v8 is not documented. Change-Id: I9cf51ddf0934869ed3ba6214b8d6a383dab8a11c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3281260Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Johann Koenig <johannkoenig@google.com> Cr-Commit-Position: refs/heads/main@{#77892}
-
Dominik Inführ authored
Complete implementation of Heap::MakeHeapIterable() by also making the LABs of paged spaces iterable. This method is the one to use when the heap and/or a particular space shall be iterable. Bug: v8:12338 Change-Id: Id859cf1a05df21a54939c504c59d7b1ccd659c9b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3277888Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/main@{#77891}
-
Andreas Haas authored
With eager compilation, CompilationEventCallbacks get released when all compilation units in the compilation state are finished. This is possible because no future compilation event could get triggered after that. With dynamic tiering, though, the {FinishedCompilationChunk} event can trigger repeatedly, even after all compilation units finish at some point in time, as dynamic tiering can create new CompilationUnits. As a temporary fix, CompilationEventCallbacks don't get released when dynamic tiering is enabled. This CL fixes this issue by turning the callback from an std::function into a class, and adding a second function to the class which indicates whether the callback can be released when all compilation units in the compilation state are finished. Thereby all callbacks can be deallocated except the ones like the code caching callback which waits for the {FinishedCompilationChunk} events. R=jkummerow@chromium.org Bug: v8:12289 Change-Id: I0f73f4bd2dffe644c9a26c274cb52ac6fa49ab67 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3264288 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#77890}
-
Manos Koukoutos authored
In each wasm CallDescriptor, we store the signature of the call based on the real parameters passed to the call. This signature is more precise than the formal function signature. We use this signature in inlining to enable more optimizations. Changes: - Add wasm_sig_ field to CallDescriptor. - Construct the real signature in {DoCall} and {DoReturnCall} in graph-builder-interface, and pass it to all call-related functions in WasmGraphBuilder. - Update {ReplaceTypeInCallDescriptorWith} to use ValueType over MachineType. Construct the updated function signature. - In wasm-inlining, kill the Call node after inlining. - Add two tests. Bug: v8:11510 Change-Id: Ica711b6b4d83945ecb7201be26577eab7db3c060 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3270539Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/main@{#77889}
-
JianxiaoLuIntel authored
Change-Id: I2c05683f2172cc4a37189382ad886f523d51e823 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3273814Reviewed-by: Shu-yu Guo <syg@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Auto-Submit: Jianxiao Lu <jianxiao.lu@intel.com> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#77888}
-
v8-ci-autoroll-builder authored
Rolling v8/third_party/google_benchmark/src: https://chromium.googlesource.com/external/github.com/google/benchmark/+log/a17480d..8401429 Remove bazelbuild/rules_cc dependency (#1283) (Teodor Spæren) https://chromium.googlesource.com/external/github.com/google/benchmark/+/8401429 Support for building with LLVM clang-10/clang-11 on Windows. (#1227) (Alisenai) https://chromium.googlesource.com/external/github.com/google/benchmark/+/926f61d TBR=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com,mlippautz@chromium.org Change-Id: I8bf8ac6270221ea56ab065bb7acedd7dbe8f43f8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3281561Reviewed-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/main@{#77887}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/2c7b246..d134d68 TBR=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: Id7ae91bc1ac02eac6b9e5efe0c89b6e3a07a766b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3281560Reviewed-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/main@{#77886}
-
- 14 Nov, 2021 1 commit
-
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/701766c..2c7b246 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/08a95d8..3fca89b Rolling v8/third_party/googletest/src: https://chromium.googlesource.com/external/github.com/google/googletest/+log/9ca071b..1b18723 Rolling v8/tools/luci-go: git_revision:bf56a119c5f056a1f7a04c8dbe19cdd86728b540..git_revision:4cf9fa8105d30e3a6855bbfca50c5d6f88efb6b2 Rolling v8/tools/luci-go: git_revision:bf56a119c5f056a1f7a04c8dbe19cdd86728b540..git_revision:4cf9fa8105d30e3a6855bbfca50c5d6f88efb6b2 TBR=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: I59ae20fdf916dc2d1fd24cb6c5fd3229d252b466 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3279044Reviewed-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/main@{#77885}
-
- 13 Nov, 2021 1 commit
-
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/f38f611..701766c Rolling v8/third_party/aemu-linux-x64: eWKIKAWWZAJd3aNVfwGevVWupHnf0a31BNfVmvJfkucC.._9UC-vP_2UFSwkJLesq9YhIVywjThQvItoADZJtdSUcC Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/279fe4e..a7ad5b5 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/0b187dc..08a95d8 Rolling v8/third_party/instrumented_libraries: https://chromium.googlesource.com/chromium/src/third_party/instrumented_libraries/+log/380f371..e09c4b6 Rolling v8/third_party/zlib: https://chromium.googlesource.com/chromium/src/third_party/zlib/+log/6da1d53..f8964a5 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/92efe5e..32d7c38 TBR=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: I1242a5a0b8efa55c9fa5c979c107122b84407b31 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3279042Reviewed-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/main@{#77884}
-
- 12 Nov, 2021 20 commits
-
-
Jakob Kummerow authored
FLAG_wasm_dynamic_tiering is still off by default. When enabled, it now uses the technique previously behind --new-wasm-dynamic-tiering. Bug: v8:12281 Change-Id: I365c2c066e62418cd6abc7830f95d1fe0f950e33 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3275570 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#77883}
-
Igor Sheludko authored
The entered contexts stack must be in sync with the flags stack. Bug: chromium:1269225 Change-Id: Ibb522286b47866d5f13aaec1a0a02914c13a5545 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3279680 Commit-Queue: Igor Sheludko <ishell@chromium.org> Commit-Queue: Shu-yu Guo <syg@chromium.org> Auto-Submit: Igor Sheludko <ishell@chromium.org> Reviewed-by: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/main@{#77882}
-
Shu-yu Guo authored
When incrementally marking a non-shared heap, shared values should not be marked. Similarly, non-shared values should not be marked when incrementally marking a shared heap. Bug: v8:11708 Change-Id: Iecd799e7e3060e5fb3897b8be0c4e8158d9ff57f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3278673 Commit-Queue: Shu-yu Guo <syg@chromium.org> Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/main@{#77881}
-
Ng Zhi An authored
Bug: v8:12244,v8:12245 Change-Id: I4a57fbd187ffebb1c1f170865641caef7b193926 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3274017 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/main@{#77880}
-
Junliang Yan authored
Change-Id: I8cd279059800567a81d8586944c8ed4c0ef9fa92 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3279101Reviewed-by: Milad Fa <mfarazma@redhat.com> Commit-Queue: Junliang Yan <junyan@redhat.com> Cr-Commit-Position: refs/heads/main@{#77879}
-
Ng Zhi An authored
Bug: v8:12244,v8:12245 Change-Id: I02e08e79a7b3a07531bfac753beff13a866247e8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3269170Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/main@{#77878}
-
Igor Sheludko authored
Under certain conditions GC could flush bytecode array from SharedFunctionInfos. This CL ensures that the bytecode array is always available for reconstructing source positions. Bug: chromium:1265570 Change-Id: I2ce7eb04201f69121687ab0aaa2af42adb2caae0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3275569Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#77877}
-
Thibaud Michaud authored
Switching stack affects all instances, therefore make the active continuation a root object instead of an instance field. Bug: v8:12191 Change-Id: Ia521bf4e7c3cbca035f916e47804c2f75bbd8f18 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3268296Reviewed-by: Andreas Haas <ahaas@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/main@{#77876}
-
Ng Zhi An authored
This shadows ATOM used in js-regxp. Making this an enum class requires changing a lot of different places. Atom is an Intel brand name, so INTEL_ATOM kinda make sense. Bug: v8:12244,v8:12245 Change-Id: I80be342488328cde5aaca36f900375d2fb381253 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3276926Reviewed-by: Maya Lekova <mslekova@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/main@{#77875}
-
Milad Fa authored
Change-Id: Iff669f6272e2a95d5150108d5a3a77e903afbeb9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3275568Reviewed-by: Junliang Yan <junyan@redhat.com> Commit-Queue: Milad Fa <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/main@{#77874}
-
Victor Gomes authored
UnprotectAndRegisterMemoryChunk should only be called if we have CodePageCollectionMemoryModificationScope or CodeSpaceMemoryModificationScope open. This also fixes cctests that create code objects without a code modification scope. Bug: v8:12054 Change-Id: Id931f1f8120050b2bb76ef3d5701b9a32e52ff37 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3277882 Auto-Submit: Victor Gomes <victorgomes@chromium.org> Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/main@{#77873}
-
Leszek Swirski authored
Unify parse post-processing between main-thread and background-thread parsing, now that we have LocalIsolate and can Internalize on background threads. As part of this, simplify the LocalIsolate parking pattern to explicitly park during ParseOnBackground, rather than being implicitly parked when ParseOnBackground is called. This reduces the amound of scoping needed in the BackgroundCompileTask::Run method. Change-Id: Ifdb128b763129bda78bd1bae89dac1c62f872350 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3277876 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/main@{#77872}
-
Victor Gomes authored
When closing a concurrent allocator, for instance when closing a LocalHeap, we need to make the LAB of the code space iterable. We add then a CodePageMemoryModificationScope to allow code space modification. Bug: v8:12054 Change-Id: I438d7c1a50694930b7558dec2dd552bec22b7552 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3277887 Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/main@{#77871}
-
Dominik Inführ authored
Speculative fix for a data race involving memory measurement. For memory measurement we use JSGlobalObject::native_context_unchecked in NativeContextInferrer::InferForJSObject when trying to infer the NativeContext for a JS object from a concurrent marking thread. This load can race e.g. with the context deserializer running on the main thread. Fix this race by making the load relaxed atomic. Bug: chromium:1269681 Change-Id: Id04a92572d7d722594b2f8465e579b7231e54e29 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3277885 Auto-Submit: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#77870}
-
Leszek Swirski authored
Due to streaming, the SFI enqueueing can happen concurrently with with main-thread finalising, so we need to add locks around accesses to the SFI->Job map. Bug: v8:12370 Change-Id: I60281a954ef10f7fcde559b9529077a6b9a82c31 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3277874 Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Victor Gomes <victorgomes@chromium.org> Cr-Commit-Position: refs/heads/main@{#77869}
-
Frank Tang authored
Diary https://docs.google.com/document/d/1NqMw7DAVFCZRx67auC7sgOvrikHvCYuaB87JUf21yG8/edit# https://chromium.googlesource.com/chromium/deps/icu.git/+log/eedbaf76..3e05d9da chromium roll in https://chromium-review.googlesource.com/c/chromium/src/+/3224333 Bug: chromium:1260116 Change-Id: Ie1922a129310106985f3bf1bffd9101fce6bb73a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3237532Reviewed-by: Shu-yu Guo <syg@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/main@{#77868}
-
Michael Lippautz authored
The DCHECK ensures that a page that is going to be destroyed is not anymore part of the vector of pages of a space. This DCHECK runs while a potential concurrent sweeper task may add a page for a live object to the vector, resulting in a broken iteration. Use the pages lock to fix this. Bug: chromium:1268969 Change-Id: Ice87026957b3e6b5d36cf28293f7aa6901e96ba2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3277132 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Anton Bikineev <bikineev@chromium.org> Cr-Commit-Position: refs/heads/main@{#77867}
-
Michael Achenbach authored
No-Try: true Bug: v8:12054 Change-Id: I118d1680939d1282c580530f8aa12a4cf72e54d1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3277875Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#77866}
-
Yujie Wang authored
- Add Wasm SIMD packing instruction: `LiftoffAssembler::emit_i8x16_{s,u}convert_i16x8` - Add Wasm SIMD unpacking instructions: `LiftoffAssembler::emit_i64x2_{s,u}convert_i32x4_{low,high}` `LiftoffAssembler::emit_i32x4_{s,u}convert_i16x8_{low,high}` `LiftoffAssembler::emit_i64x2_{s,u}convert_i32x4_{low,high}` - Add RVV instrucions: `vzext_vf{2,4,8}` and `vsext_vf{2,4,8}` - Fixed simulator for `vslidedown_vi` Bug: v8:11976 Change-Id: Idd383bc566589ce183f4fcef2201d2ccfe03519f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3273812Reviewed-by: ji qiu <qiuji@iscas.ac.cn> Reviewed-by: Yahan Lu <yahan@iscas.ac.cn> Commit-Queue: ji qiu <qiuji@iscas.ac.cn> Cr-Commit-Position: refs/heads/main@{#77865}
-
v8-ci-autoroll-builder authored
Rolling v8/third_party/google_benchmark/src: https://chromium.googlesource.com/external/github.com/google/benchmark/+log/b3c08f6..a17480d Fix dependency typo and unpin cibuildwheel version in wheel building … (#1263) (Nicholas Junge) https://chromium.googlesource.com/external/github.com/google/benchmark/+/a17480d TBR=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com,mlippautz@chromium.org Change-Id: Iee5b0189f850eba665fe60670b0bdaa7e5a3f779 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3275844Reviewed-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/main@{#77864}
-