- 21 Aug, 2021 3 commits
-
-
Yu Yin authored
Port commit 6a487504 Change-Id: Icfff8241e6e920970f0168ebfae535291c4d9e72 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3111275Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/main@{#76418}
-
Yu Yin authored
Port commit 6a487504 Change-Id: I6fd1a15f1f35fd3b8cd3cfb72d7c428d018273c8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3109087Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/536c882..d4924be Rolling v8/buildtools: https://chromium.googlesource.com/chromium/src/buildtools/+log/6f9b470..88e9a29 Rolling v8/buildtools/third_party/libc++abi/trunk: https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libcxxabi/+log/671803f..e4b161d Rolling v8/buildtools/third_party/libunwind/trunk: https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libunwind/+log/83f8edb..5f26300 Rolling v8/third_party/aemu-linux-x64: JV2fBSeIQc_xaqKsVDvLIvDmvx2ejeL-Y75N37PloLMC..6VzMt4Yj2cR2686nGtmYD_6idAkR2f0lTHjpGAYPr1oC Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/77a7089..ebf22ea Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/c4e2b36..52b4510 Rolling v8/third_party/googletest/src: https://chromium.googlesource.com/external/github.com/google/googletest/+log/0134d73..2f80c2b Rolling v8/third_party/jinja2: https://chromium.googlesource.com/chromium/src/third_party/jinja2/+log/6ac5f7e..6db8da1 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/f1ab49b..6002926 Rolling v8/tools/luci-go: git_revision:a5735121c6339dee9b1b3644535e230744daaac9..git_revision:24b519169c7848dbeae2dba04698c41666388a45 Rolling v8/tools/luci-go: git_revision:a5735121c6339dee9b1b3644535e230744daaac9..git_revision:24b519169c7848dbeae2dba04698c41666388a45 Rolling v8/tools/luci-go: git_revision:a5735121c6339dee9b1b3644535e230744daaac9..git_revision:24b519169c7848dbeae2dba04698c41666388a45 TBR=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com Change-Id: I3cb55842d72cf0e8bd892f0cce24ebd5c8465cbc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3111616Reviewed-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@{#76416}
-
- 20 Aug, 2021 16 commits
-
-
Michael Lippautz authored
Consider reading the internal node pointer instead of the actual pointer when trying to figure out whether a node needs to be destroyed. This preserves the non-atomiticity of the actual pointer which highlights races using TSAN while fixing destruction. Bug: chromium:1239081 Change-Id: I1d1fa29d40d86e4b156269abc90142ee71a8d8f4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3110199 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Omer Katz <omerkatz@chromium.org> Cr-Commit-Position: refs/heads/main@{#76415}
-
Adam Klein authored
This reverts commit 6ae18c2d. Reason for revert: breaks a bunch of tests on Mac arm64 bots: https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Mac%20-%20arm64%20-%20release/5754/overview https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Mac%20-%20arm64%20-%20debug/2421/overview Original change's description: > [wasm] Move write scope out of NativeModule::AddCode > > {NativeModule::AddCode} is a central method that should usually be > called in batches, where the caller holds a {CodeSpaceWriteScope} for a > longer time (over several compilations). > This CL moves us closer to that by removing the scope from that central > method and instead putting it in callers where it becomes more visible. > There are already TODOs to introduce caching or batching to avoid some > switching, and one more TODO is added. > > Drive-by: Remove an unneeded {CodeSpaceMemoryModificationScope}. > > R=jkummerow@chromium.org > > Bug: v8:11974 > Change-Id: Ia13c601abc766e5fca6ca053bf1fc4d647b53ed0 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3098186 > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> > Commit-Queue: Clemens Backes <clemensb@chromium.org> > Cr-Commit-Position: refs/heads/master@{#76344} Bug: v8:11974 Change-Id: Ia6a6814f153f7602d5d691bc5c930601ff4622a7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3111268 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/main@{#76414}
-
Nico Weber authored
Bug: chromium:1066980 Change-Id: I4e149f5dd9ac2d3b8f51afd2c63451d509441e64 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3110652 Commit-Queue: Nico Weber <thakis@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Auto-Submit: Nico Weber <thakis@chromium.org> Reviewed-by:
Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/main@{#76413}
-
Santiago Aboy Solanes authored
End of an era https://www.youtube.com/watch?v=jbf9ZYi8eac Change-Id: I64eb201a9073df55564a3ba38ac5511974485c08 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3103316Reviewed-by:
Dan Elphick <delphick@chromium.org> Reviewed-by:
Adam Klein <adamk@chromium.org> Commit-Queue: Adam Klein <adamk@chromium.org> Auto-Submit: Santiago Aboy Solanes <solanes@chromium.org> Cr-Commit-Position: refs/heads/main@{#76412}
-
Michael Lippautz authored
Avoids emitting scopes when not even running. This can be a problem for metrics computation which may recursively invoke EnsureSweepingCompleted() when starting marking even though the sweeper is guaranteed to be not running at this point. Bug: chromium:1211795 Change-Id: I8d7692f4e8c640f38d3c52df5c111fff4f06df9e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3109674 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
-
Nico Weber authored
Bug: chromium:1066980 Change-Id: Ib7d38cb46f25b69431fa965eb6b951af3f24bc95 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3111005 Auto-Submit: Nico Weber <thakis@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by:
-
Al Muthanna Athamina authored
Add infra-staging flag to test runner which adds the no-fail flag. This will be used to see the accuracy of numfuzz builders when we ignore exit code 1. Bug: v8:11826 Change-Id: I6684331efe9c801d02716d94cb16e8ba816d9c68 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3110196Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Almothana Athamneh <almuthanna@chromium.org> Cr-Commit-Position: refs/heads/main@{#76409}
-
Al Muthanna Athamina authored
Bug: v8:12013 Change-Id: Ied041acd5e8898eae0beca2d2b49b90846b3f047 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3110191 Commit-Queue: Almothana Athamneh <almuthanna@chromium.org> Auto-Submit: Almothana Athamneh <almuthanna@chromium.org> Reviewed-by:
-
Milad Fa authored
Port 6a487504 Original Commit Message: This is a reland of faf2208a Changes since revert: - Fix arm64 codegen for full pointer mode Original change's description: > [compiler] Support acq/rel accesses and atomic accesses on tagged > > This CL adds an AtomicMemoryOrder parameter to the various atomic load > and store operators. Currently only acquire release (kAcqRel) and > sequentially consistent (kSeqCst) orders are supported. > > Additionally, atomic loads and stores are extended to work with tagged > values. > > This CL is a pre-requisite for supporting atomic accesses in Torque, > which is in turn a pre-requisite for prototyping shared strings. > > Bug: v8:11995 > Change-Id: Ic77d2640e2dc7e5581b1211a054c93210c219355 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3101765 > Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> > Reviewed-by: Zhi An Ng <zhin@chromium.org> > Commit-Queue: Shu-yu Guo <syg@chromium.org> > Cr-Commit-Position: refs/heads/main@{#76393} R=syg@chromium.org, joransiu@ca.ibm.com, junyan@redhat.com, midawson@redhat.com BUG= LOG=N Change-Id: I859320f1e752a8e79a0855ecad8651c635092f46 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3108289Reviewed-by:
Junliang Yan <junyan@redhat.com> Commit-Queue: Junliang Yan <junyan@redhat.com> Cr-Commit-Position: refs/heads/main@{#76407}
-
Seth Brenith authored
The heap snapshot view in the dev tools reports some incorrect retaining paths involving weak references from relocation data in Code objects. This change updates IndexedReferencesExtractor::VisitEmbeddedPointer to better match the behavior in MarkingVisitorBase. Drive-by cleanup: ObjectVisitor::VisitRelocInfo needn't be virtual because there's only one implementation. Bug: v8:12126 Change-Id: I669a7408e7a46e797b8c2b372235b4ea42ee22e1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3107214Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Seth Brenith <seth.brenith@microsoft.com> Cr-Commit-Position: refs/heads/main@{#76406}
-
Victor Gomes authored
No-Try: true Change-Id: Ie9ccef9034d42c483c4d39aa949c85811fd65d9a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3109678Reviewed-by:
Patrick Thier <pthier@chromium.org> Commit-Queue: Patrick Thier <pthier@chromium.org> Auto-Submit: Victor Gomes <victorgomes@chromium.org> Cr-Commit-Position: refs/heads/main@{#76405}
-
Jakob Kummerow authored
Combining parts in a balanced-binary-tree like order allows us to use fast multiplication algorithms. Bug: v8:11515 Change-Id: I6829929671770f009f10f6f3b383501fede476ab Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3049079Reviewed-by:
Maya Lekova <mslekova@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#76404}
-
Al Muthanna Athamina authored
The skipped tests have been flaking on the last ten runs on V8 NumFuzz - debug. Bug: v8:11826 Change-Id: I925c8e581b34c1b08fb295856278e506b8d62f26 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3103305 Auto-Submit: Almothana Athamneh <almuthanna@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Liviu Rau <liviurau@chromium.org> Reviewed-by:
-
Lu Yahan authored
Change-Id: I5b3001cebcf97a239c259af7fc4ddc889c9a84a2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3108947 Commit-Queue: Ji Qiu <qiuji@iscas.ac.cn> Reviewed-by:
Ji Qiu <qiuji@iscas.ac.cn> Cr-Commit-Position: refs/heads/main@{#76402}
-
v8-ci-autoroll-builder authored
Rolling v8/third_party/google_benchmark/src: https://chromium.googlesource.com/external/github.com/google/benchmark/+log/c4b06e5..8fd49d6 Fix a -Wunreachable-code-aggressive warning (#1214) (Nico Weber) https://chromium.googlesource.com/external/github.com/google/benchmark/+/8fd49d6 TBR=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com,mlippautz@chromium.org Change-Id: I1442e530778245ed2252fbed092147dd496e61da Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3108868Reviewed-by:
-
Lu Yahan authored
Port 3107220: Reland "[compiler] Support acq/rel accesses and atomic accesses on tagged" | 3107220 Change-Id: I190f6b62458b0abe193ca7f5ea9d6912117439fe Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3108945Reviewed-by:
-
- 19 Aug, 2021 21 commits
-
-
Shu-yu Guo authored
This is a reland of faf2208a Changes since revert: - Fix arm64 codegen for full pointer mode Original change's description: > [compiler] Support acq/rel accesses and atomic accesses on tagged > > This CL adds an AtomicMemoryOrder parameter to the various atomic load > and store operators. Currently only acquire release (kAcqRel) and > sequentially consistent (kSeqCst) orders are supported. > > Additionally, atomic loads and stores are extended to work with tagged > values. > > This CL is a pre-requisite for supporting atomic accesses in Torque, > which is in turn a pre-requisite for prototyping shared strings. > > Bug: v8:11995 > Change-Id: Ic77d2640e2dc7e5581b1211a054c93210c219355 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3101765 > Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> > Reviewed-by: Zhi An Ng <zhin@chromium.org> > Commit-Queue: Shu-yu Guo <syg@chromium.org> > Cr-Commit-Position: refs/heads/main@{#76393} Bug: v8:11995 Change-Id: I23577486334fec6b08fb3a2f5be1f6e5e16db11b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3107220Reviewed-by:
-
Ng Zhi An authored
Fixed: v8:12095 Bug: v8:12095 Change-Id: If2021397000958ccdd058b99ce8f4d6e8d4d2836 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3097106Reviewed-by:
Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/main@{#76398}
-
Ng Zhi An authored
Whenever we are adding a new AddressRegion to the CodeMap, we first remove all overlapping regions. The logic to check for overlapping region is incomplete. For example, if all existing regions are less than the region to be added, we incorrectly remove all regions, effectively deleting all JITCodeEntry we have constructed. We extract this overlapping check into a helper function, so that we can unittest this without worrying about JITCodeEvent functionality, and also without dealing with V8 internals (like Isolate and SFI). The overlapping logic is rather hard to understand, has many special cases, it will probably be much easier to just loop through all the entries, rather than using lower_bound. Ideally, we can refactor this to use some sort of sweep-line algorithm. Hopefully the unittests catch the most obvious cases. Bug: v8:11908 Change-Id: Id96975599ac59974185c3dbf64cdfceb17e98d18 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3105381 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#76397}
-
Ross McIlroy authored
Change-Id: I32fc41124c6c16efe1150d60e72dc2bba90782c7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3106745Reviewed-by:
Hannes Payer <hpayer@chromium.org> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/main@{#76396}
-
Ross McIlroy authored
Change-Id: Ie96be7e4d1c37de92cbb6271fb0c8779ea9d4ae4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3106746Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Reviewed-by:
Shu-yu Guo <syg@chromium.org> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/main@{#76395}
-
Nico Hartmann authored
This reverts commit faf2208a. Reason for revert: https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux64%20-%20arm64%20-%20sim%20-%20pointer%20compression/10870/overview Original change's description: > [compiler] Support acq/rel accesses and atomic accesses on tagged > > This CL adds an AtomicMemoryOrder parameter to the various atomic load > and store operators. Currently only acquire release (kAcqRel) and > sequentially consistent (kSeqCst) orders are supported. > > Additionally, atomic loads and stores are extended to work with tagged > values. > > This CL is a pre-requisite for supporting atomic accesses in Torque, > which is in turn a pre-requisite for prototyping shared strings. > > Bug: v8:11995 > Change-Id: Ic77d2640e2dc7e5581b1211a054c93210c219355 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3101765 > Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> > Reviewed-by: Zhi An Ng <zhin@chromium.org> > Commit-Queue: Shu-yu Guo <syg@chromium.org> > Cr-Commit-Position: refs/heads/main@{#76393} Bug: v8:11995 Change-Id: Id9936672f9e96c509b1cdf866de1ac5303996945 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3107229Reviewed-by:
Nico Hartmann <nicohartmann@chromium.org> Commit-Queue: Nico Hartmann <nicohartmann@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#76394}
-
Shu-yu Guo authored
This CL adds an AtomicMemoryOrder parameter to the various atomic load and store operators. Currently only acquire release (kAcqRel) and sequentially consistent (kSeqCst) orders are supported. Additionally, atomic loads and stores are extended to work with tagged values. This CL is a pre-requisite for supporting atomic accesses in Torque, which is in turn a pre-requisite for prototyping shared strings. Bug: v8:11995 Change-Id: Ic77d2640e2dc7e5581b1211a054c93210c219355 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3101765Reviewed-by:
-
Patrick Thier authored
- Introduce helper to push arguments onto the stack (Standalone this change doesn't make a lot of sense, but is in preparation for including the receiver in argc). - Introduce helper to shift arguments already on the stack to make room for new arguments (Varargs). - arm64 is not included because a) there was already a helper similar to ShiftArguments and b) PushArguments is not similar enough to make sense for arm64 because of small differences (e.g. also pushing the function) in conjunction with stack alignment. Drive-by: Use masm DropArguments in Sparkplug EmitReturn Bug: v8:11112 Change-Id: Id7a3a5f025abb19e2a52dae27b3b484fe87e9faf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3097275Reviewed-by:
Victor Gomes <victorgomes@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Commit-Queue: Patrick Thier <pthier@chromium.org> Cr-Commit-Position: refs/heads/main@{#76392}
-
Jakob Kummerow authored
It must be possible to determine an object's size on the heap without relying on the presence of any other objects. Specifically, if an object and its WasmTypeInfo die at the same time, they can be swept in any order, and the sweeper may need to know their sizes. This patch solves the problem by repurposing two bytes in the Map, where WasmStructs can store their instance size, and WasmArrays can store their element size (which can be used to compute their size). Fixed: chromium:1240670 Change-Id: Ib960fd0a409936aff1aef4daafed4c38b8497880 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3106649 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#76391}
-
Yu Yin authored
TEST: externref-globals-liftoff wasm-gc-breakpoints with --stress-incremental-marking Change-Id: Ia5956588a008155f199bad98b1aff6e593fcd7ee Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3106785 Auto-Submit: Yu Yin <xwafish@gmail.com> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Reviewed-by:
-
Milad Fa authored
Passing directories to fopen is not a defined behaviour in C/C++. A new test case added by https://crrev.com/c/3098189 is trying to import directories which is expected to fail. Test however is not passing on some platforms including on S390 Linux as `fopen` is successful, size gets set to 0 and a (non-existent) empty file gets returned. This CL uses `stat` to make sure the path is valid and is not a directory. Change-Id: Ibcc762b21145d2198cba07953387a31f39f59300 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3102346Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Milad Fa <mfarazma@redhat.com> Cr-Commit-Position: refs/heads/main@{#76389}
-
Victor Gomes authored
No-Try: true Change-Id: I429066dd039519d4195c8d8a09559a720b818976 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3106748 Auto-Submit: Victor Gomes <victorgomes@chromium.org> Reviewed-by:
-
Jakob Kummerow authored
Some of the Array benchmarks were unintentionally spending a lot of time on Number-to-String conversions. This patch avoids that, by computing the dynamically-created strings only once. Bug: chromium:1240981 Change-Id: If10826813d555398b45c22c958dee27e17f35d3c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3106747Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#76387}
-
Jakob Gruber authored
.. and decrease the include-ball size. Change-Id: Id35358a6882156f6684475b7f0b0193f8ca5eaf5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3103313 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Jakob Kummerow authored
Operator::kEliminatable has the unfortunate consequence that depending on surrounding code, the allocating builtin call could get scheduled before the max length check, causing a crash instead of a trap. Fixed: chromium:1239954 Change-Id: Ice2e3e4f67e8fce44a886c0079e0e31f124c02b0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3103315Reviewed-by:
Georg Neis <neis@chromium.org> Reviewed-by:
Manos Koukoutos <manoskouk@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#76385}
-
Paolo Severini authored
Functions CopyAndConvertArrayToCppBufferInt32 and CopyAndConvertArrayToCppBufferFloat64 used by specializations of template functions TryCopyAndConvertArrayToCppBuffer were removed with https://chromium-review.googlesource.com/c/v8/v8/+/3056988. Bug: v8:11739 Change-Id: I495b8878780adb7d2274cc733c7d4c5938171eb7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3095651 Commit-Queue: Paolo Severini <paolosev@microsoft.com> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/main@{#76384}
-
Camillo Bruni authored
This fix consists of 2 parts: a) Fix async hooks: - Allow initialising the promise hook properties - Do not call async hooks if we're overflowing the stack b) Avoid some more recursion when reporting the stack trace Bug: chromium:1240723 Change-Id: Icedfc8b48655bacc3f79591944e3869b85f1c4de Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3103321Reviewed-by:
-
Michael Lippautz authored
HAS_PROGRESS_BAR is set after page initialization at which point all flags are assumed to be immutable while a GC is running. Separating out the progress bar from flags allows setting it lazily at allocation time. Bug: v8:11915 Change-Id: I48a877e0e80d583d7a0fadef2546fc70417806e7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3085268 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/third_party/google_benchmark/src: https://chromium.googlesource.com/external/github.com/google/benchmark/+log/990299f..c4b06e5 Set theme jekyll-theme-minimal (Dominic Hamon) https://chromium.googlesource.com/external/github.com/google/benchmark/+/c4b06e5 wrap things that look like tags but aren't with `{% raw %}` (Dominic Hamon) https://chromium.googlesource.com/external/github.com/google/benchmark/+/0fb4b75 TBR=v8-waterfall-sheriff@grotations.appspotmail.com,mtv-sf-v8-sheriff@grotations.appspotmail.com,mlippautz@chromium.org Change-Id: I54b77aef6cbfb4593e9853086c293b168b4fb503 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3105448Reviewed-by:
-
Samuel Groß authored
Bug: chromium:1218005 Change-Id: I533e9fccc48767f4fccc8746e182682abd36c5e5 Cq-Include-Trybots: luci.v8.try:v8_linux64_heap_sandbox_dbg_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3106387Reviewed-by:
-
Jakob Gruber authored
The JSRegExp heap object should not be the source of truth for regexp flags, which are also relevant in places that don't need or want to care about the heap object layout (e.g.: the regexp parser). Introduce RegExpFlags as a new source of truth, and base everything else on these flags. As a first change, remove the js-regexp.h dependency from the regexp parser. Other files in src/regexp/ should be updated in follow-up work. Change-Id: Id9a6706c7f09e93f743b08b647b211d0cb0b9c76 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3103306Reviewed-by:
-
