- 26 Jan, 2022 24 commits
-
-
Joyee Cheung authored
When reparsing the class scope to collect initializers in sloppy mode, the class scope may still have a scope info without any allocated variables. If its outer scope doesn't have an outer scope (which means the outer scope in the optimized scope chain becomes the script scope), we should also set the scope info in the script scope as is done in Scope::DeserializeScopeChain() for the scope resolution. Bug: chromium:1290587, v8:10704 Change-Id: I7804d53f330e59d4ab0405a11b132569f348b55d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3413647Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Joyee Cheung <joyee@igalia.com> Cr-Commit-Position: refs/heads/main@{#78784}
-
Michael Achenbach authored
No-Try: true Bug: chromium:1256445 Change-Id: If028ec562fe10769e9a3a2dcdba9cf2074cd72a1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3417435 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Auto-Submit: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Liviu Rau <liviurau@chromium.org> Commit-Queue: Liviu Rau <liviurau@chromium.org> Cr-Commit-Position: refs/heads/main@{#78783}
-
Alessandro Pignotti authored
This patch takes advantage of memory information from the module to avoid unnecessary reloads of the SSA environment after a Wasm call. As far as I can sse, the SSA envinronment consists of the mem_start and mem_size values. Both these values cannot ever change if: initial_mem_size == max_mem_size. Although this should be obviously true for memories defined in the module itself, some explanation may be necessary for imported memories. During module instantiation, the imported memory is checked as part of InstanceBuilder::ProcessImportedMemory. The following properties are verified: 1) The current size of the imported memory is >= the initial declared size 2) The maximal size of the imported memory is <= the maximal declared size The effective maximal limit will be min(imported_max, declared_max), hence the optimization will only trigger if the imported memory is already as large as it can be. Since memory growth is impossible, there is no point in reloading the environment anyway. Change-Id: Ie6c6ad278175d253b61131972a6db7530bd52b90 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3412082Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#78782}
-
Camillo Bruni authored
web-snapshot.js is sometimes causing timeouts, splitting the test files to prevent this. Bug: v8:12554, v8:11525 Change-Id: I53f8476eab9bd009689f056eabcdfa549c509a0d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3416248Reviewed-by: Maya Lekova <mslekova@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#78781}
-
Victor Gomes authored
Change-Id: Ic214ef7ca9bcc543b98f26e77f31ad12f80798fb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3417430 Auto-Submit: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#78780}
-
Victor Gomes authored
Adds the archs fuchsia_x64 and fuchsia_arm64. No-Try: true Change-Id: I5e12a436fc206fecc910965e9597b7e05be23e26 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3416247 Auto-Submit: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#78779}
-
Milad Fa authored
On AIX, calling mmap on a pre-designated address with MAP_FIXED will fail and return -1 unless the application has requested SPEC1170 compliant behaviour with arguments such as `XPG_SUS_ENV=ON`. Therefore an AIX specific implementation has been added under platform-aix.cc. Change-Id: Ib5b8a19a3a9e6d202aed7e792c00a25ddc547c72 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3403045Reviewed-by: Samuel Groß <saelo@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Milad Farazmand <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/main@{#78778}
-
Marja Hölttä authored
Bug: v8:11525 Change-Id: I765923f6d15959a7fc6ceddd9a6d60338316300a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3416246Reviewed-by: Camillo Bruni <cbruni@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#78777}
-
Michael Achenbach authored
This reverts commit fd608d18. Reason for revert: https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux64%20UBSan%20-%20builder/838/overview Original change's description: > [ext-code-space] Enable external code space on x64 and desktop arm64 > > Perf Sheriffs: this CL might regress some benchmarks while improving > the others. > > Bug: v8:11880 > Change-Id: I857526d0971fc858b56126cbc276d9bd4157d71f > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3416244 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Igor Sheludko <ishell@chromium.org> > Cr-Commit-Position: refs/heads/main@{#78774} Bug: v8:11880 Change-Id: Ie1009824936a65790e743cbc01ca2e5bec5dec90 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3417432 Auto-Submit: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#78776}
-
Thibaud Michaud authored
R=ahaas@chromium.org CC=fgm@chromium.org Bug: v8:12191, v8:12344 Change-Id: Ibbc1077afa8de89f9acb39675451a61f3ceea413 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3412090Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/main@{#78775}
-
Igor Sheludko authored
Perf Sheriffs: this CL might regress some benchmarks while improving the others. Bug: v8:11880 Change-Id: I857526d0971fc858b56126cbc276d9bd4157d71f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3416244Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#78774}
-
Nico Hartmann authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/841e388..1c8bf90 Rolling v8/buildtools/linux64: git_revision:80a40b07305373617eba2d5878d353532af77da3..git_revision:0725d7827575b239594fbc8fd5192873a1d62f44 Rolling v8/buildtools/third_party/libc++abi/trunk: https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libcxxabi/+log/7d79126..e4cc353 Rolling v8/buildtools/third_party/libunwind/trunk: https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libunwind/+log/efb2cbd..c8a5d43 Rolling v8/third_party/android_platform: https://chromium.googlesource.com/chromium/src/third_party/android_platform/+log/5023a5c..f0d4a3b Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/8bc3659..d90eeee Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/a657331..d05a2e0 Rolling v8/third_party/googletest/src: https://chromium.googlesource.com/external/github.com/google/googletest/+log/100f6fb..f45d586 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/df50898..5518918 Rolling v8/tools/luci-go: git_revision:5b02a4aaeb5fd78d6fe41d6d54d1cb58da17f192..git_revision:09f8b3edbbf18dc63d0d5aa7722ae7acc20b11b4 Rolling v8/tools/luci-go: git_revision:5b02a4aaeb5fd78d6fe41d6d54d1cb58da17f192..git_revision:09f8b3edbbf18dc63d0d5aa7722ae7acc20b11b4 R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: Ia9d43ad1b668bfa8e7172d2265d10204a43d895d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3412230 Owners-Override: Nico Hartmann <nicohartmann@chromium.org> Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> Reviewed-by: Maya Lekova <mslekova@chromium.org> Commit-Queue: Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/heads/main@{#78773}
-
Igor Sheludko authored
1) when generating short builtin calls/jumps assemblers should use the offset from the CodeRange base rather than the start of the code range reservation because otherwise it's not guaranteed that the PC-relative offset will fit into architecture's constraints. The code range reservation start could be different from the code range base in the following cases: * when the "base bias size" is non-zero (on Windows 64), * when we ended up over-reserving the address space for the code range, which happens as a last resort to fulfil the CodeRange alignment requirements. See the VirtualMemoryCage description for details. Drive-by fixes: 2) in case of over-reserving address space for external code range, the pre-calculated hint for where the remapped embedded builtins should be copied to was outside of the allocatable CodeRange region and thus useless. The fix is to use the allocatable region instead of the reservation region when calculating the hint. 3) when allocating CodeRange with zero base bias size we can create the VirtualMemory reservation from the first attempt simply by passing the required base alignment to the VirtualMemory constructor. Bug: v8:11880, chromium:1290591 Change-Id: If341418947e2170d967e22b38bcc371594939c1c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3412089Reviewed-by: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#78772}
-
Marja Hölttä authored
Bug: v8:11525 Change-Id: I4df5144a7d0ed2b68cf15c7bfd72ce4a17ad4e41 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3416237Reviewed-by: Camillo Bruni <cbruni@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#78771}
-
Jochen Eisinger authored
Change-Id: Ib4fd3bc66f5451ac2c50d550515992bdfbe41fcc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3414772Reviewed-by: Camillo Bruni <cbruni@chromium.org> Commit-Queue: Jochen Eisinger <jochen@chromium.org> Cr-Commit-Position: refs/heads/main@{#78770}
-
Camillo Bruni authored
Use DescriptorArray::Set instead of Append to avoid resorting the descriptors for every newly added property Bug: v8:11525 Change-Id: Id6d113f6218e095125256a8c7c8cfb28c8b41ae5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3415391Reviewed-by: Marja Hölttä <marja@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#78769}
-
Dominik Inführ authored
Map::Hash relies on the fact that the map space is never compacted. However this might change in the future, so instead of using the address of the prototype's map, we use the prototype's identity hash instead. Bug: v8:12578 Change-Id: Ia4961ed55119681c0033aa187789f6710ff2d22c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3412085Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Cr-Commit-Position: refs/heads/main@{#78768}
-
Marja Hölttä authored
Exports are properties in the global object. Pre-reserve the space, since we know the count upfront. Bug: v8:11525 Change-Id: Ia8ea992234ed8cf71a1060254766b0ba31562436 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3416231Reviewed-by: Camillo Bruni <cbruni@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#78767}
-
Manos Koukoutos authored
Bug: v8:7748 Change-Id: Iee5afc3ce21f3a09fdb810beb6a73123bf21afdf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3401594Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/main@{#78766}
-
v8-ci-autoroll-builder authored
Rolling v8/third_party/google_benchmark/src: https://chromium.googlesource.com/external/github.com/google/benchmark/+log/57b2bfa..d0fbf8a Cache PerfCounters instance in PerfCountersMeasurement (#1308) (Liqiang TAO) https://chromium.googlesource.com/external/github.com/google/benchmark/+/d0fbf8a R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com,mlippautz@chromium.org Change-Id: I982279bd209fedfaf72a8ce674818906eb60147d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3416710 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@{#78765}
-
Hao Xu authored
In current BitwiseSmi bytecodes the code to do Smi operation is inside a loop. This CL fast path the Smi operation by peeling the first Smi check out of the loop, and avoid Smi->Int->Smi conversion where possible. Drive-by fix: Add CSA_DCHECK in Smi shift to avoid unexpected use. Bug: v8:12442 Change-Id: I1adce560fb22a4409337e2958779eccf9197e4ff Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3328784Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Hao A Xu <hao.a.xu@intel.com> Cr-Commit-Position: refs/heads/main@{#78764}
-
Camillo Bruni authored
- Use raw pointer when setting the SFI in CreateJSFunction - Use some more factory->xxx_value() handle accessor to avoid handle creation Bug: v8:11525 Change-Id: I5ed62f56cf2e53cc765566c0c129c7851b704813 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3401591Reviewed-by: Marja Hölttä <marja@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#78763}
-
Nico Hartmann authored
This reverts commit 5320fe8d. Reason for revert: https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux%20-%20debug/38175/overview Original change's description: > Reland "[string] Support shared strings in Value{Serializer,Deserializer}" > > This is a reland of 3cb4039c > > Changes since revert: > - Fix FLAG_stress_scavenge interaction with shared Isolate > - Use the shared Isolate's global handles to keep shared values > alive in transit during a postMessage > > Original change's description: > > [string] Support shared strings in Value{Serializer,Deserializer} > > > > When FLAG_shared_string_table is true, postMessaging strings will share > > instead of copy. > > > > Note that not all operations on shared strings are supported, and shared > > strings may be slower than non-shared strings for some operations. > > > > Bug: v8:12007 > > Change-Id: I3462128e15410d2568868143571571b3025722c1 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3277250 > > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > > Commit-Queue: Shu-yu Guo <syg@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#78614} > > Bug: v8:12007 > Change-Id: I5d9b99b2dac6f26d5ef046d7aec94f1a1d219419 > Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_rel_ng > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3389533 > Reviewed-by: Camillo Bruni <cbruni@chromium.org> > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Shu-yu Guo <syg@chromium.org> > Cr-Commit-Position: refs/heads/main@{#78761} Bug: v8:12007 Change-Id: Ie8e54b30055324e6592562450b51d5a11e11c9d0 Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_rel_ng No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3416232 Auto-Submit: Nico Hartmann <nicohartmann@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Nico Hartmann <nicohartmann@chromium.org> Owners-Override: Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/heads/main@{#78762}
-
Shu-yu Guo authored
This is a reland of 3cb4039c Changes since revert: - Fix FLAG_stress_scavenge interaction with shared Isolate - Use the shared Isolate's global handles to keep shared values alive in transit during a postMessage Original change's description: > [string] Support shared strings in Value{Serializer,Deserializer} > > When FLAG_shared_string_table is true, postMessaging strings will share > instead of copy. > > Note that not all operations on shared strings are supported, and shared > strings may be slower than non-shared strings for some operations. > > Bug: v8:12007 > Change-Id: I3462128e15410d2568868143571571b3025722c1 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3277250 > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Shu-yu Guo <syg@chromium.org> > Cr-Commit-Position: refs/heads/main@{#78614} Bug: v8:12007 Change-Id: I5d9b99b2dac6f26d5ef046d7aec94f1a1d219419 Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_rel_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3389533Reviewed-by: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/main@{#78761}
-
- 25 Jan, 2022 10 commits
-
-
Milad Fa authored
Implementations are added to macro-assembler to be shared between liftoff and code generator. Change-Id: I6bde65dc50f1e52b8fbca150854e0b0863dff301 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3416190Reviewed-by: Junliang Yan <junyan@redhat.com> Commit-Queue: Milad Farazmand <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/main@{#78760}
-
Igor Sheludko authored
Drive-by: fix multi-arch build. Bug: v8:11880 Change-Id: I4e56370598117fec2a0131e5638d4bac3d84c52f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3412083Reviewed-by: Samuel Groß <saelo@chromium.org> Auto-Submit: Igor Sheludko <ishell@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#78759}
-
Adam Klein authored
Change-Id: Idce43801ef5f2f3e194a63cea3522eb6710b681e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3413192Reviewed-by: Hannes Payer <hpayer@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/main@{#78758}
-
legendecas authored
1. Expose all the functions to empty builtins. 2. Wire up the basic structure of ShadowRealm and internal slots. Bug: v8:11989 Change-Id: If7545fe18a74b2bd4b70a1a25776e41f03aaff89 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3195532Reviewed-by: Shu-yu Guo <syg@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Chengzhong Wu <legendecas@gmail.com> Cr-Commit-Position: refs/heads/main@{#78757}
-
Michael Lippautz authored
The hello world sample needs to initialize V8's default platform in case it is not built as stand-alone example. Bug: v8:12427 Change-Id: I78b68fbed2c2a25b0ff03675beb94dfc5b9b4135 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3412088Reviewed-by: Omer Katz <omerkatz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#78756}
-
Manos Koukoutos authored
Change-Id: I1289fcab6c4812868258b14492d85bad20ae7e9f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3406536Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/main@{#78755}
-
Samuel Groß authored
When sandboxed external pointers are enabled, external pointers now only require 32 bits of storage space in a HeapObject. This CL does not shrink the size of EmbedderDataSlots, which will happen in a follow-up CL. Bug: v8:10391 Change-Id: I3cf8b68c3b985cf806a45183717f50462a88c281 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/+/3359629Reviewed-by: Igor Sheludko <ishell@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Maya Lekova <mslekova@chromium.org> Commit-Queue: Samuel Groß <saelo@chromium.org> Cr-Commit-Position: refs/heads/main@{#78754}
-
Anton Bikineev authored
The check finds implicit conversions of integer literals to bools: bool b1 = 1; bool b2 = static_cast<bool>(1); and transforms them to: bool b1 = true; bool b2 = true; Bug: chromium:1290142 Change-Id: I1fec7d7a6f25af23e9b9aac687f5896e79f17b51 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3406533 Auto-Submit: Anton Bikineev <bikineev@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/main@{#78753}
-
Lu Yahan authored
Bug: v8:12576 Change-Id: I4d63f85d6528f2ad5e6502fffbc5fc7d797818ed Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3412562Reviewed-by: ji qiu <qiuji@iscas.ac.cn> Commit-Queue: ji qiu <qiuji@iscas.ac.cn> Auto-Submit: Yahan Lu <yahan@iscas.ac.cn> Commit-Queue: Yahan Lu <yahan@iscas.ac.cn> Cr-Commit-Position: refs/heads/main@{#78752}
-
v8-ci-autoroll-builder authored
Rolling v8/third_party/google_benchmark/src: https://chromium.googlesource.com/external/github.com/google/benchmark/+log/acd7562..57b2bfa Fix some errors in Custom Statistics demo code. (#1332) (YuanYingdong) https://chromium.googlesource.com/external/github.com/google/benchmark/+/57b2bfa R=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com,mlippautz@chromium.org Change-Id: I6682b979c23ce45e6a365371b5d5818b4b3fc3f4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3413460 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@{#78751}
-
- 24 Jan, 2022 6 commits
-
-
Junliang Yan authored
Change-Id: I505026e562cda584aad7e56d1dd02f26b42ddf17 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3412808Reviewed-by: Milad Farazmand <mfarazma@redhat.com> Commit-Queue: Junliang Yan <junyan@redhat.com> Cr-Commit-Position: refs/heads/main@{#78750}
-
Junliang Yan authored
Change-Id: I9a4ba92f9da9cc964056d5c563b0534d9d172fcb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3412809Reviewed-by: Milad Farazmand <mfarazma@redhat.com> Commit-Queue: Junliang Yan <junyan@redhat.com> Cr-Commit-Position: refs/heads/main@{#78749}
-
Milad Fa authored
Implementations are added to macro-assembler to be shared between liftoff and code generator. Change-Id: I3fac2b82686836106cefa9a78f5feda6105679d4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3412359Reviewed-by: Junliang Yan <junyan@redhat.com> Commit-Queue: Milad Farazmand <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/main@{#78748}
-
Marja Hölttä authored
Bug: v8:11111 Change-Id: I83778377f1343a6157bf01f13b99ffcb41e4c6d6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3404778Reviewed-by: Shu-yu Guo <syg@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/main@{#78747}
-
Milad Fa authored
Implementations are added to macro-assembler to be shared between liftoff and code generator. Change-Id: Ia26b82de3f0af076ace3d53e285917029d2d5ac4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3407794Reviewed-by: Junliang Yan <junyan@redhat.com> Commit-Queue: Milad Farazmand <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/main@{#78746}
-
Joyee Cheung authored
This is a reland of 91f08378 When the class scope does not need a context, the deserialized outer scope of the initializer scope would not be the class scope, and we should not and do not need to use it to fix up the allocation information of the context-allocated variables. The original patch did not consider this case and resulted in a regression when we tried to reparse the initializer function to look for destructuring assignment errors. This fixes the regression by not deserializing the class scope that's going to be reparsed, and using the positions of the scopes to tell whether the scope info matches the reparsed scope and can be used to fix up the allocation info. Original change's description: > [class] implement reparsing of class instance member initializers > > Previously, since the source code for the synthetic class instance > member initializer function was recorded as the span from the first > initializer to the last initializer, there was no way to reparse the > class and recompile the initializer function. It was working for > most use cases because the code for the initializer function was > generated eagarly and it was usually alive as long as the class was > alive, so the initializer wouldn't normally be lazily parsed. This > didn't work, however, when the class was snapshotted with > v8::SnapshotCreator::FunctionCodeHandling::kClear, > becuase then we needed to recompile the initializer when the class > was instantiated. This patch implements the reparsing so that > these classes can work with FunctionCodeHandling::kClear. > > This patch refactors ParserBase::ParseClassLiteral() so that we can > reuse it for both parsing the class body normally and reparsing it > to collect initializers. When reparsing the synthetic initializer > function, we rewind the scanner to the beginning of the class, and > parse the class body to collect the initializers. During the > reparsing, field initializers are parsed with the full parser while > methods of the class are pre-parsed. > > A few notable changes: > > - Extended the source range of the initializer function to cover the > entire class so that we can rewind the scanner to parse the class > body to collect initializers (previously, it starts from the first > field initializer and ends at the last initializer). This resulted > some expectation changes in the debugger tests, though the > initializers remain debuggable. > - A temporary ClassScope is created during reparsing. After the class > is reparsed, we use the information from the ScopeInfo to update > the allocated indices of the variables in the ClassScope. > > Bug: v8:10704 > Change-Id: Ifb6431a1447d8844f2a548283d59158742fe9027 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2988830 > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Joyee Cheung <joyee@igalia.com> > Cr-Commit-Position: refs/heads/main@{#78299} Bug: chromium:1278086, chromium:1278085, v8:10704 Change-Id: Iea4f1f6dc398846cbe322adc16f6fffd6d2dfdf3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3325912Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Joyee Cheung <joyee@igalia.com> Cr-Commit-Position: refs/heads/main@{#78745}
-