commit | d0bbb62b0659778bdf7b05725e1b29c4fd829c97 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Wed Dec 04 03:46:36 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Dec 04 03:46:36 2024 |
tree | c8890c1cb4527a72dff2d422c5fe33615115be3f | |
parent | 79d7101e2e058ac83c1e3b64cb9f4a043d9d2072 [diff] |
Roll llvm-libc from d4fe74b8c2c8 to 4c70d6b5a62a (1 revision) https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libc.git/+log/d4fe74b8c2c8..4c70d6b5a62a 2024-12-04 huberjn@outlook.com [libc] Fix the GPU build when building inside the NATIVE project (#118573) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/llvm-libc-chromium Please CC aeubanks@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: aeubanks@google.com Change-Id: I2585cc05163b47dedc488648c0d446600bc25a76 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6068264 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@{#1391440}
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.