Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 17 commits
- 44 files changed
- 9 contributors
Commits on May 27, 2022
-
Merged: [mips][liftoff] Fix atomic ops implementation error
LLd and Scd should be used for StoreType::kI64Store* types. (cherry picked from commit 207f489) Bug: v8:12904 Change-Id: Ib09e2b720e441679b568a356cf8937b6241626fc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3661522 Commit-Queue: Liu Yu <liuyu@loongson.cn> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/branch-heads/10.2@{#8} Cr-Branched-From: 374091f-refs/heads/10.2.154@{#1} Cr-Branched-From: f0c353f-refs/heads/main@{#79976}
Commits on Jun 3, 2022
-
Merged: [ic] handle access check for private names
Previously the LookupIterator ignores private symbols (including private names) for the access check. This patch removes these exceptions so that they are always checked. Drive-by: removes the unused should_throw parameter in Runtime::DefineObjectOwnProperty() Bug: chromium:1321899 (cherry picked from commit bb98b38) Change-Id: I21f22c003a6e156ab2448a5232e37ffd709a7492 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3687698 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/branch-heads/10.2@{#10} Cr-Branched-From: 374091f-refs/heads/10.2.154@{#1} Cr-Branched-From: f0c353f-refs/heads/main@{#79976}
-
Merged: Squashed multiple commits.
Merged: [wasm] Fix return value of lazy compile runtime function Revision: 22a16bd Merged: [loong64][mips][wasm] Fix return value of lazy compile runtime function Revision: 7e50fa6 Merged: PPC/s390: [wasm] Fix return value of lazy compile runtime function Revision: 68ae81b Merged: [riscv64] Fix return value of lazy compile runtime function Revision: bdb2062 R=jkummerow@chromium.org Bug: chromium:1311960 Change-Id: I7556b2867051931029b0ede1aba5b5321d097c82 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3687697 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/branch-heads/10.2@{#12} Cr-Branched-From: 374091f-refs/heads/10.2.154@{#1} Cr-Branched-From: f0c353f-refs/heads/main@{#79976}
Commits on Jun 6, 2022
-
Merged: [profiling] Create process-unique CPU profile ids
In https://crrev.com/c/3522896 we changed the last_id_ to be a member variable. This subtly changed how profile id's were generated. This CL changes this part back to a static variable that guarantees process-wide unique profile ids. Bug: chromium:1330726, chromium:1297283 (cherry picked from commit f1c4fd3) Change-Id: Ie1314ab576668cfc550f8bf12a15803dc17b4405 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3688397 Commit-Queue: Shu-yu Guo <syg@chromium.org> Reviewed-by: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/branch-heads/10.2@{#14} Cr-Branched-From: 374091f-refs/heads/10.2.154@{#1} Cr-Branched-From: f0c353f-refs/heads/main@{#79976}
Commits on Jun 10, 2022
-
Merged: [weakrefs] Set unregister_token to undefined when unregistering
(cherry picked from commit dd3289d) Bug: chromium:1321078 Change-Id: Ic7537cc5101b35018911c27a81e9b0e0a7da154b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3695262 Reviewed-by: Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/branch-heads/10.2@{#16} Cr-Branched-From: 374091f-refs/heads/10.2.154@{#1} Cr-Branched-From: f0c353f-refs/heads/main@{#79976}
Commits on Jun 14, 2022
-
Version 10.2.154.10 (cherry-pick)
Merged 85b4b5d [compiler] only enable MidTierRegisterAllocator for Wasm Bug: chromium:1335054 Change-Id: I61ab97d4fbfcbb81319e611a64a6454e050a1d65 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3705397 Owners-Override: Tobias Tebbi <tebbi@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/10.2@{#18} Cr-Branched-From: 374091f-refs/heads/10.2.154@{#1} Cr-Branched-From: f0c353f-refs/heads/main@{#79976}
Commits on Jun 24, 2022
-
Merged: [compiler] make CanCover() transitive
In addition to checking that a node is owned, CanCover() also needs to check if there are any side-effects in between the current node and the merged node. When merging inputs of inputs, this check was done with the wrong side-effect level of the in-between node. We partially fixed this before with `CanCoverTransitively`. This CL addresses the issue by always comparing to the side-effect level of the node from which we started, making `CanCoverTransitively` superfluous. Bug: chromium:1336869 (cherry picked from commit 6048f75) Change-Id: I63cf6bfdd40c2c55921db4a2ac737612bb7da4e4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3722095 Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/branch-heads/10.2@{#19} Cr-Branched-From: 374091f-refs/heads/10.2.154@{#1} Cr-Branched-From: f0c353f-refs/heads/main@{#79976}
Commits on Jun 27, 2022
-
Merged: [wasm] Decrement current_int_param_slot only once for reftypes
R=thibaudm@chromium.org (cherry picked from commit 5e3abf4) Bug: chromium:1335523 Change-Id: I194915b37ea27b3d7d1a9f2367b6935b8a3bff39 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3702233 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#81095} Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3726213 Cr-Commit-Position: refs/branch-heads/10.2@{#21} Cr-Branched-From: 374091f-refs/heads/10.2.154@{#1} Cr-Branched-From: f0c353f-refs/heads/main@{#79976}
Commits on Jul 1, 2022
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 10.2.154.4...10.2.154.13