commit | a916cf0612c0f7198b618b129739fc97641943a4 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Sun Aug 14 01:03:41 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sun Aug 14 01:03:41 2022 |
tree | 945b5adcff14c0441edba018670ce30d82527b73 | |
parent | 0fbfaf105ff7d83d152d9f1adda2d611540731a1 [diff] |
Roll libunwind from 754d0167693b to 030b4ebf3239 (1 revision) https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libunwind.git/+log/754d0167693b..030b4ebf3239 2022-08-12 xingxue@outlook.com [libunwind][AIX] Implement _Unwind_FindEnclosingFunction() using traceback table on AIX 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: I4cfbce394403af2834bd077e5eaa33300a4aeafc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3830939 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@{#1034855}
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.