commit | 00d5b1f5d20731b092c33e3e38c11f7a7dded2bd | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Apr 24 09:30:44 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 24 09:30:44 2025 |
tree | 4d84229365f048e33fc7e1c456f8c877ea6893e2 | |
parent | a908d58762ee6fdd82b0d4d35a7fe53b4d677565 [diff] |
Roll compiler-rt from 70ee4ad2abd1 to c9899c370674 (1 revision) https://chromium.googlesource.com/external/github.com/llvm/llvm-project/compiler-rt.git/+log/70ee4ad2abd1..c9899c370674 2025-04-24 camsyn@foxmail.com [TSan, SanitizerBinaryMetadata] Analyze the capture status for `alloca` rather than arbitrary `Addr` (#132756) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/compiler-rt-chromium Please CC lexan@google.com,zequanwu@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry 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 Tbr: zequanwu@google.com Change-Id: I99d7bb073fd5cfd19cb672d928a82df1c32cd379 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6485760 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@{#1451024}
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.