commit | 9bfbbffdba73668fdb483e5a850911d2b64c35d7 | [log] [tgz] |
---|---|---|
author | Daniel Cheng <dcheng@chromium.org> | Tue May 30 20:22:27 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 30 20:22:27 2023 |
tree | c3c82da08cd429c4574588813cdf35ea694973ba | |
parent | 9da90d2b7e14e8203a6e480c8f5ed0c88111b21e [diff] |
Disable usage of `__is_cpp17_contiguous_iterator` until libc++ rolls. Though names prefixed with `__` are reserved for implementation use, specializing `__is_cpp17_contiguous_iterator` is currently the only way to tell libc++ that `memcpy()` can be safe to use with a custom iterator. Without this workaround, there are noticeable regressions, e.g. when using std::copy() with spans of trivially copyable types (see https://crbug.com/994174). However, https://reviews.llvm.org/D150801 renames this template to `__libcpp_is_contiguous_iterator`, which blocks rolling past this libc++ revision. As a workaround, temporarily forward declare and specialize both variants. ` In addition, C++20 provides an official way for a custom iterator to opt into these types of optimizations, using `iterator_concept`, so also go ahead and opt `CheckedContiguousIterator` into using this. Bug: 1449299 Bug: b/284031070 Change-Id: If4e667fca8d1475ce5ced76b6072134686d12f4a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4570684 Commit-Queue: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/main@{#1150815}
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.