Roll V8 from 6ae153942c55 to 1a5ed2013963 (6 revisions) https://chromium.googlesource.com/v8/v8.git/+log/6ae153942c55..1a5ed2013963 2024-08-13 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Version 12.9.174 2024-08-13 victorgomes@chromium.org [maglev] Allow object tracking inside a loop 2024-08-13 victorgomes@chromium.org [test] Make test less brittle 2024-08-13 jkummerow@chromium.org [wasm][cleanup] Move two functions to Factory 2024-08-13 victorgomes@chromium.org [maglev] Don't change object that other objects depends on 2024-08-13 saelo@chromium.org [sandbox][leaptiering] Allocate dispatch entries in JSFunctionBuilder If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/v8-chromium-autoroll Please CC liviurau@google.com,machenbach@google.com,v8-waterfall-gardener@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:linux-blink-rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:dawn-linux-x64-deps-rel Change-Id: Id62e722c2685cdfc5254b37c23a836555bf375b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5786266 Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1341196}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.