- 20 Sep, 2022 9 commits
-
-
Simon Zünd authored
This CL introduces a new root that is conceptually a WeakMap<ScopeInfo, Tuple2<ScopeInfo, StringSet>> Instead of storing the "locals block list" for debug-evaluate on the `ScopeInfo` object directly, we will store it instead in a global WeakMap. This enables us to re-use the "locals block lists" across multiple debug-evaluate invocations without having to modify the `ScopeInfo` of `SharedFunctionInfo`s. R=bmeurer@chromium.org Doc: https://bit.ly/chrome-devtools-debug-evaluate-design Bug: chromium:1363561 Change-Id: Ib52f9abd97cf1c8fa3053ff3c61a6062c4b814be Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3902041Reviewed-by:
Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/main@{#83318}
-
Leszek Swirski authored
Since we have the NodeInfo map in known_node_aspects now anyway, use it for representation changes instead of the current interpreter frame value swapping mechanism. We originally didn't want a map for representations, but if we have one anyway for node types, it makes sense to merge the two mechanisms. This also allows us to get rid of the "register same as accumulator" hack for binops, which was trying to avoid redundant representation changes, since the redundancy is removed by the node aspects mechanism automatically. It's kept for CheckedInternalizedString, since that isn't a representation change within our framework (maybe it should be?). Bug: v8:7700 Change-Id: I92491307f83d3b63fc7a210f6b8754e45d3531a7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905182Reviewed-by:
Jakob Linke <jgruber@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#83317}
-
Michael Lippautz authored
This is a reland of commit defa678e Original change's description: > cppgc: Be more conservative in Seeper::FinishIfOutOfWork > > Finalizing sweeping can be beneficial to truly end a GC cylce. We > should only finalize in `FinishIfOutOfWork()` though if that would not > introduce any jank. Limit the amount of executing finalizers in that > scenario. > > Bug: v8:13294 > Change-Id: I0237f6b6017d444c457923d83e85147c58586445 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3902222 > Commit-Queue: Michael Lippautz <mlippautz@chromium.org> > Reviewed-by: Omer Katz <omerkatz@chromium.org> > Reviewed-by: Anton Bikineev <bikineev@chromium.org> > Cr-Commit-Position: refs/heads/main@{#83279} Bug: v8:13294 Change-Id: I426a54785d1a0f569c2200156dcf41a5d5c7876f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3902583 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Omer Katz <omerkatz@chromium.org> Cr-Commit-Position: refs/heads/main@{#83316}
-
Simon Zünd authored
We currently use 1 test case per file for tests that check that debug-evaluate correctly blocks the lookup of stack-allocated variables. This CL adapts a similar approach to `debug-scopes.js`, making it easier to add new test cases in the future. R=kimanh@chromium.org Bug: chromium:1363561 Change-Id: I8ff8cfe7d59f0b9808dc02c5579e058f490553eb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3904544 Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by:
Kim-Anh Tran <kimanh@chromium.org> Cr-Commit-Position: refs/heads/main@{#83315}
-
Dominik Inführ authored
Slots in free memory need to be removed. After a GC the JS application can create additional free memory by either left- or right-trimming of heap objects. The sweeper might discover memory that was freed because of such operations. In case the sweeper discovers free memory, there can't be any recorded slots in it. Otherwise subsequent allocations might store untagged values in those slots and the next deref would most likely crash. Remove OLD_TO_SHARED slots in freed memory when left-trimming, right- trimming and for DeleteObjectPropertyFast. Also full GC was right-trimming objects which now needs to remove slots in OLD_TO_SHARED. Bug: v8:11708 Change-Id: I5761336e103704929fbd455d74bdbb499ae23f61 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905144Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/main@{#83314}
-
jameslahm authored
Allow non-registered symbols as keys in weakmap and weakset. Allow non-registered symbols as target and unregisterToken in WeakRef and FinalizationRegistry. Bug: v8:12947 Change-Id: Ieb63bda66e3cc378879ac651e23300b71caed627 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3865056Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/cf385c0..29d7990 Rolling v8/third_party/fuchsia-sdk/sdk: version:9.20220918.2.1..version:9.20220919.1.1 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/b118dfd..70967a5 R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: Ib5641e39edc8bfe8f1edc6ffeebe18c2af8a9f2d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3904435 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@{#83312}
-
Frank Tang authored
The hoursInDay could be fractional number on the date of changng daylight saving time for time zone in half hours or some historical time zone. Ex: Australia/Lord_Howe on Sunday, April 3, 2022, 2:00:00 am clocks were turned backward 0:30 hours to Sunday, April 3, 2022, 1:30:00 am local standard time instead. so that day will have 24.5 hours. On Sunday, October 2, 2022, 2:00:00 am clocks are turned forward 0:30 hours to Sunday, October 2, 2022, 2:30:00 am local daylight time instead. So the hoursInDay for that day is only 23.5 hours. Historically, Singapore from 1933 to 1941 moved clocks forward 20 minutes for daylight savings, resulting the day in 24.33333 and 23.66667 hours. Test covered in https://github.com/tc39/test262/blob/main/test/staging/Temporal/ZonedDateTime/old/dst-properties.js Change the return type from MaybeHandle<Smi> to MaybeHandle<Object> so we can return non integer value. Also change the method of division by first convert the value to second in BigInt, then divid 3600 (number of seconds in a hour) in double. Bug: v8:11544 Change-Id: Ia69d2606cd832e51f415a00440fb9cbc236883e4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3901619Reviewed-by:
Adam Klein <adamk@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/main@{#83311}
-
Frank Tang authored
Refactor the interface between intl and Temporal and pass the nanosecond in BigInt to intl. Approximate the nanoseconds to the correct close by millisecond depending on the usage before calling ICU API and convert the result millisecond into BigInt in nanosecond before return from intl. Remove Maybe for function always complete. Bug: v8:11544 Change-Id: Icc471b80312c513c9415b690804aa624df4a387d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3897165Reviewed-by:
-
- 19 Sep, 2022 23 commits
-
-
Michael Lippautz authored
Test was using concurrent sweeper which could lead to the concurrent sweeper holding onto memory until the allocation succeeded in rare cases. Bug: v8:13308 Change-Id: I0f9f93cc503cdc17d6962b3c31bc4ea698b4cb42 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905183 Auto-Submit: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Omer Katz <omerkatz@chromium.org> Reviewed-by:
-
Dominik Inführ authored
This method will be used in the marking visitors to stop marking into the shared heap from e.g. worker or client heaps. Bug: v8:13267 Change-Id: I7a099a3f816fa5d867d6a99558838389914e3048 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3904606 Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by:
-
Camillo authored
Make sure both the fast and slow version return the same value in case of wrong follow-bit values in the input. Bug: chromium:1359230, chromium:1360735 Change-Id: Ic65f81109e5bbc288fa41a5540ec7e6cece10ffc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3890998 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Samuel Groß <saelo@chromium.org> Cr-Commit-Position: refs/heads/main@{#83307}
-
Junliang Yan authored
Change-Id: I20ea43a62e051599ab7860acd34ba55f6d355ae7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3904426Reviewed-by:
Igor Sheludko <ishell@chromium.org> Commit-Queue: Junliang Yan <junyan@redhat.com> Commit-Queue: Igor Sheludko <ishell@chromium.org> Auto-Submit: Junliang Yan <junyan@redhat.com> Cr-Commit-Position: refs/heads/main@{#83306}
-
Leszek Swirski authored
This reverts commit d7fcbba8. Reason for revert: Speculatively reverting because of blocked roll Original change's description: > [sandbox] Increase ExternalPointerTable maximum capacity to 512MB > > Bug: v8:10391 > Change-Id: I383e11bdccf6fcaf13f29d25e1404545067d313e > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3891249 > Reviewed-by: Igor Sheludko <ishell@chromium.org> > Commit-Queue: Samuel Groß <saelo@chromium.org> > Cr-Commit-Position: refs/heads/main@{#83203} Bug: v8:10391 Change-Id: Id3a374a1f87a6ec3889d2e81d169ad004744ca99 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3904605 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#83305}
-
Jakob Linke authored
Missing deps were causing correctness issues due to missed deopts. In this CL, we reuse PropertyAccessInfo creation to create appropriate dependencies. Bug: v8:7700 Change-Id: Ic6c20df01fa8a36f677aed80791fcea1ccc4b512 Fixed: v8:13289 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3904603Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Jakob Linke <jgruber@chromium.org> Cr-Commit-Position: refs/heads/main@{#83304}
-
Jakob Linke authored
For the 'finish compilation' event for all tiers (SP, ML, TF), consistently use the 'completed compiling' message prefix. For deoptimization, print the Code object in addition to the JSFunction (now that deopts may happen in both ML and TF). Bug: v8:7700 Change-Id: I3375db91413195c92007db9b1b202af9bd6ac05a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3904601 Auto-Submit: Jakob Linke <jgruber@chromium.org> Reviewed-by:
-
Igor Sheludko authored
... which will contain all compression scheme related functions. This will allow introducing custom compression schemes for certain cases and use the compression scheme class as a template argument for TaggedField or OffHeapCompressedObjectSlot implementations. Bug: v8:7703, v8:11880 Change-Id: Ic78d36b7021110d6a4797a3150547a224d942b32 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3899262Reviewed-by:
-
Shu-yu Guo authored
ArrayBuffers of length 0 may not have a BackingStore, so guard for that case in ArrayBuffer.prototype.transfer. Bug: v8:11111, chromium:1364738 Change-Id: I058d00f0f60183f9137c60682ad93973c7a6dcbb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3902517 Auto-Submit: Shu-yu Guo <syg@chromium.org> Reviewed-by:
Marja Hölttä <marja@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#83301}
-
Marja Hölttä authored
Bug: v8:8888,v8:1360042 Change-Id: I9524f8e99c4239e196066ee49547623a37f8f261 Fixed: v8:1360042 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3898998 Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by:
-
Matthias Liedtke authored
This change tests all JavaScript language constructs and builtins in combination with the unwrapped Wasm objects. For JavaScript, excluding some basic introspection (e.g. `Object.isExtensible`) WebAssembly GC objects are treated opaque. They can be passed around freely but don't allow any access to properties, elements etc. This behavior is currently exposed only if the `wasm-gc-js-interop` flag is set. Bug: v8:7748 Change-Id: If0dc368f99d4097e3eaf53edde4e244e3081e334 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3879616Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Nico Hartmann <nicohartmann@chromium.org> Commit-Queue: Matthias Liedtke <mliedtke@chromium.org> Cr-Commit-Position: refs/heads/main@{#83299}
-
Tobias Tebbi authored
Bug: v8:12783, chromium:1364943 Change-Id: Ia972708e0679cf68e32d8e3c2cf103ab11aac2b8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3899087Reviewed-by:
Darius Mercadier <dmercadier@chromium.org> Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Auto-Submit: Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Darius Mercadier <dmercadier@chromium.org> Cr-Commit-Position: refs/heads/main@{#83298}
-
Leszek Swirski authored
The parallel move optimizer tries to use the scratch register to store cycle breaks, but needs to spill the value if the scratch register is needed for stack->stack moves. Whether this spill happened is supposed to be tracked with the scratch_has_cycle_start_ field, but the update of this field was missing. Bug: v8:7700 Change-Id: I2dc8d9186c9ec8ca03104fd3ae972a38924670ed Fixed: chromium:1364783 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3899086 Commit-Queue: Jakob Linke <jgruber@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Michael Achenbach authored
No-Try: true Change-Id: I51acce0dde9c706135a45cbdb6514d2ed9df2574 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3902043 Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#83296}
-
Michael Achenbach authored
This reverts commit defa678e. Reason for revert: Blocks roll: https://ci.chromium.org/ui/p/v8/builders/ci/Linux%20V8%20FYI%20Release%20(NVIDIA)/21307/overview Original change's description: > cppgc: Be more conservative in Seeper::FinishIfOutOfWork > > Finalizing sweeping can be beneficial to truly end a GC cylce. We > should only finalize in `FinishIfOutOfWork()` though if that would not > introduce any jank. Limit the amount of executing finalizers in that > scenario. > > Bug: v8:13294 > Change-Id: I0237f6b6017d444c457923d83e85147c58586445 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3902222 > Commit-Queue: Michael Lippautz <mlippautz@chromium.org> > Reviewed-by: Omer Katz <omerkatz@chromium.org> > Reviewed-by: Anton Bikineev <bikineev@chromium.org> > Cr-Commit-Position: refs/heads/main@{#83279} Bug: v8:13294 Change-Id: Ic3cf7e105a076ef41b35a075d8f35918bc412588 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3902582 Owners-Override: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
-
Igor Sheludko authored
... and report an error if the profile file can't be opened for writing. Also, overwrite the profile file instead of appending if the file exists. Bug: v8:10470 Change-Id: I0da0ee8d901a0c477b7f71ba23436243f93bd0ee Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3902521 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Auto-Submit: Igor Sheludko <ishell@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#83294}
-
Leszek Swirski authored
Lazy deopts are always after calls, so force them to spill their inputs. This would normally be the case anyway, except for deferred calls, which don't tell the register allocator to spill like normal calls do. This makes lazy deopt regalloc always spill its inputs and use their spill slot, but unlike calls, this doesn't additionally clear the register, so subsequent nodes can continue using the register cached value without having to reload it. As drive-bys, fix the Throw* opcodes to have the Throw property, and use detail::DeepForEachInput in a couple of extra locations (including for lazy deopts). Bug: v8:7700 Change-Id: I89b04f17ca781d4f69ff0ed07566fa583aa677e6 Fixed: chromium:1364074 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3899009Reviewed-by:
-
Jakob Kummerow authored
1) Inlining functions that contain stringref operations require builtin calls to be marked as kNoThrow appropriately (or have exception handling support in the graph). 2) Some overly-large inputs for string creation hit DCHECKs before getting to the places where they would have thrown an orderly exception. 3) We still had a known issue that some exceptions thrown by JS-focused code were erroneously catchable by Wasm. 4) When string.concat attempted to create a too-long string, it ran into a DCHECK because we didn't clear the "thread in wasm" flag. 5) The builtin call for string.concat was erroneously marked as kEliminatable, which could cause the trap get eliminated. Bug: v8:12868 Change-Id: Iad3ada0e2465bfd8f3d00bb064c32049d6b19d87 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3902522 Auto-Submit: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Andy Wingo <wingo@igalia.com> Reviewed-by:
Andy Wingo <wingo@igalia.com> Cr-Commit-Position: refs/heads/main@{#83292}
-
Leszek Swirski authored
Add a conversion to int32 index for Numbers and Strings containing indices, and change the element bounds check / lookup nodes to take an int32 rather than a Smi. While we're at it, also turn the index node into an int32 index different depending on its known representation. Bug: v8:7700, v8:13287 Change-Id: Ie98502d58f789873d42f8801499e78bf777db70f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3900012 Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#83291}
-
Leszek Swirski authored
Bug: v8:7700 Change-Id: I1f607b929068e249d26df3529f676da301c79a91 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3900011 Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/third_party/fuchsia-sdk/sdk: version:9.20220917.2.1..version:9.20220918.2.1 R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: Ieee97fe2a91f90bc7602f81507fb6dab73c6de67 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3903335 Bot-Commit: 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@{#83289}
-
JialuZhang-intel authored
Let jump threading phase be able to handle the jump with gap moves instructions. Record the first occurrence of the gap jump instruction and forward the same gap jump instructions into the recorded one. For example: In this case, we merge the second instruction into the first one, because those two gap jump instructions have the same gap moves. -- Before jump threading phase: B0: 1. gap(rdx=rbx) ArchJmp imm:3 B1: 2. gap(rdx=rbx) ArchJmp imm:3 -- After jump threading phase: B0: 1. gap(rdx=rbx) ArchJmp imm:3 B1: 2. ArchNop This can eliminate redundant jump and move instructions. Design doc: https://docs.google.com/document/d/1SpO7Kw4e6CnCesFT118MUnCufUHZDy3QaVSymcci5jE/edit?usp=sharing Change-Id: Ie94c8f63e2f758824619f6ed9513cbdff00186c4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3858528Reviewed-by:Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Jialu Zhang <jialu.zhang@intel.com> Cr-Commit-Position: refs/heads/main@{#83288}
-
Lu Yahan authored
If trap cover 32bit compare, it will emit 3 archopcode(shl shl trap) and don't emit right source position on Trap opcode. Change-Id: I5dd1a89d133688ca315360b8d8123d561782d623 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3903733Reviewed-by:
ji qiu <qiuji@iscas.ac.cn> Commit-Queue: ji qiu <qiuji@iscas.ac.cn> Auto-Submit: Yahan Lu <yahan@iscas.ac.cn> Cr-Commit-Position: refs/heads/main@{#83287}
-
- 18 Sep, 2022 2 commits
-
-
JianxiaoLuIntel authored
Can reduce 1 byte instruction size. Change-Id: Ie97841c5011d91e295e756aef4b45b62c3ec52f4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3885956Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/843261b..cf385c0 Rolling v8/buildtools: https://chromium.googlesource.com/chromium/src/buildtools/+log/92ea83b..9e95466 Rolling v8/buildtools/third_party/libc++/trunk: https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libcxx/+log/e73c465..d128f2b Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/421c4fe..18bdadc Rolling v8/third_party/fuchsia-sdk/sdk: version:9.20220916.1.1..version:9.20220917.2.1 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/c3b78bc..b118dfd R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: I0474c3176189c9245220bf5682a75e78cb20d8da Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3903332 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@{#83285}
-
- 17 Sep, 2022 2 commits
-
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/b001130..843261b Rolling v8/buildtools: https://chromium.googlesource.com/chromium/src/buildtools/+log/813d569..92ea83b Rolling v8/buildtools/linux64: git_revision:e70d8c3d5620bc0ddcbad23a36b1b26f815ca90a..git_revision:cc28efe62ef0c2fb32455f414a29c4a55bb7fbc4 Rolling v8/buildtools/third_party/libc++/trunk: https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libcxx/+log/e2f63a1..e73c465 Rolling v8/buildtools/third_party/libunwind/trunk: https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libunwind/+log/60a480e..77b82eb Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/c067655..fcf15b9 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/dca14bc..421c4fe Rolling v8/third_party/fuchsia-sdk/sdk: version:9.20220915.2.1..version:9.20220916.1.1 Rolling v8/third_party/zlib: https://chromium.googlesource.com/chromium/src/third_party/zlib/+log/7d7ed92..8f22e90 Rolling v8/tools/luci-go: git_revision:c93fd3c5ebdc3999eea86a7623dbd1ed4b40bc78..git_revision:78063b01b53dd33a541938207b785cc86d34be37 Rolling v8/tools/luci-go: git_revision:c93fd3c5ebdc3999eea86a7623dbd1ed4b40bc78..git_revision:78063b01b53dd33a541938207b785cc86d34be37 R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: Iab1835ab4d720c4499485def6680f8cbed20fa90 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3901693 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@{#83284}
-
Frank Tang authored
https://chromium.googlesource.com/external/github.com/tc39/test262/+log/7461973..9215420 Bug: v8:7834 Change-Id: I5f830a59c57133b3c0ebe7633b60c20b00caa3ff Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3902516Reviewed-by:
Shu-yu Guo <syg@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/main@{#83283}
-
- 16 Sep, 2022 4 commits
-
-
Frank Tang authored
Return fallback while the useGrouping is "true" or "false" but throw RangeError not in the list. https://github.com/tc39/proposal-intl-numberformat-v3/pull/107 Bug: v8:13271 Change-Id: Ia325cd8fe74ff9fb501fd765e9ec2d94f8c97e38 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3886070Reviewed-by:
-
Frank Tang authored
Needed for https://chromium-review.googlesource.com/c/v8/v8/+/3893552 and also https://chromium-review.googlesource.com/c/v8/v8/+/3901196 Bug: v8:11544 Change-Id: Ieb946abde1c623e9edcca608d737e8bf65a34637 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3901195Reviewed-by:
-
Dominik Inführ authored
This CL unifies the fields for shared spaces for both the shared isolate and the shared space isolate-approach. This allows to mostly avoid separate code paths for both implementations. While this CL already sets up everything needed for allocation with --shared-space, allocation isn't fully working with this CL due to other remaining issues. Bug: v8:13267 Change-Id: Icdb40ed7045e33e6acbb97d3838fa374e6c24a2e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3892786Reviewed-by:
-
Michael Lippautz authored
Finalizing sweeping can be beneficial to truly end a GC cylce. We should only finalize in `FinishIfOutOfWork()` though if that would not introduce any jank. Limit the amount of executing finalizers in that scenario. Bug: v8:13294 Change-Id: I0237f6b6017d444c457923d83e85147c58586445 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3902222 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Anton Bikineev <bikineev@chromium.org> Cr-Commit-Position: refs/heads/main@{#83279}
-
