
1f7db7501c..74dd760826
2025-01-07 yikong@google.com [libcxx] Fix build for glibc < 2.27 (#121893)
2025-01-07 ldionne.2@gmail.com [libc++] Add new utilities to compare benchmark results between builds (#120743)
2025-01-07 dalg24@gmail.com [libc++] Improve coverage of std::atomic_ref<T>::exchange() (#121596)
2025-01-07 jannik.glueckert@gmail.com [libc++] Fix largefile handling in fs::copy_file (#121855)
2025-01-06 varconsteq@gmail.com [libc++][hardening] Add checks to `forward_list` element access. (#120858)
2025-01-06 jannik.glueckert@gmail.com [libc++] Use copy_file_range for fs::copy (#109211)
2025-01-06 ldionne.2@gmail.com [libc++] Fix the batch size used in the std::gcd benchmark (#120618)
2025-01-06 nikolasklauser@berlin.de [libc++] Simplify unwrap_ref_decay a bit (#121623)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/libcxx-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://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: hans@chromium.org,thakis@chromium.org
Change-Id: I4ceb602b559fb3fd7024382e4bac6962838bb7ca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6153123
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@{#1403239}
Chromium
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.