commit | 97aaaacd0e5055c444718b18e97ab17bf51cc63c | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Aug 14 05:50:44 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 14 05:50:44 2025 |
tree | 8c1117987b42d006bdd3b6837eaec3958875dcf1 | |
parent | 58c5998237d098f4b417d83c60f60591ed88beb9 [diff] |
Roll compiler-rt from 38c7da50caa2 to 9521218174fc (2 revisions) https://chromium.googlesource.com/external/github.com/llvm/llvm-project/compiler-rt.git/+log/38c7da50caa2..9521218174fc 2025-08-13 dan_blackwell@apple.com [sanitizer_common] Use os_log for DriverKit as os_log_error is undefined (#148848) 2025-08-13 ahmed@bougacha.org [compiler-rt] Don't run arm64e builtins tests on darwin. (#153312) 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 dloehr@google.com,lexan@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: dloehr@google.com Change-Id: If96249eb8d2cab63056681dd0510c24d011cbaa7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6848899 Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1501218}
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.