commit | e9f554741c5c0a9692cc2a9e9868ab1ad8c9a900 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Tue Nov 08 04:28:48 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Nov 08 04:28:48 2022 |
tree | 016f9800c9e87d5d016db2485369ad93279a4a7f | |
parent | b6d6e51a8b73c479aa6f8fa2f328b4e61953e8a0 [diff] |
Roll libunwind from aabcd8753678 to d08f7f8a9a28 (1 revision) https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libunwind.git/+log/aabcd8753678..d08f7f8a9a28 2022-11-08 sam@gentoo.org [CMake] Fix -Wstrict-prototypes If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/libunwind-chromium Please CC hans@chromium.org,thakis@chromium.org 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: hans@chromium.org,thakis@chromium.org Change-Id: I8ba9d4b33471aed7c11f348c4f1791becf73a9f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4011564 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@{#1068485}
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.