Roll libc++ from 76799496084d to 0a4a51e9b2b6 (11 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libcxx.git/+log/76799496084d..0a4a51e9b2b6

2024-08-14 huberjn@outlook.com [libcxx] Adjust inline assembly constraints for the AMDGPU target (#101747)
2024-08-14 huberjn@outlook.com [libcxx] Disable invalid `__start/__stop` reference on NVPTX (#99381)
2024-08-14 huberjn@outlook.com [libcxx] Add fallback to standard C when `unistd` is unavailable (#102005)
2024-08-14 ldionne.2@gmail.com [libc++] Fix ambiguous constructors for std::complex and std::optional (#103409)
2024-08-14 huberjn@outlook.com [libcxx] Set `_LIBCPP_HAS_CLOCK_GETTIME` for GPU targets (#99243)
2024-08-14 ldionne.2@gmail.com [libc++] Mechanical adjustments for the C++14 Paper status files
2024-08-14 ldionne.2@gmail.com [libc++] Remove duplicate C++17 LWG issues from the CSVs
2024-08-14 zhangyin2018@iscas.ac.cn [libc++] <experimental/simd> Add ++/-- operators for simd reference (#88091)
2024-08-13 ldionne.2@gmail.com [libc++][NFC] Add missing separators in status-tracking CSV files
2024-08-13 ldionne.2@gmail.com [libc++] Normalize how we track the meeting at which a paper of LWG issue was voted
2024-08-13 ldionne.2@gmail.com [libc++] Simplify the implementation of LWG2762 (noexcept for unique_ptr) (#102032)

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: Ic9af30e0c6b6aa9346291f093e0097b72835e3b3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5789466
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1342003}
3 files changed
tree: c243703e05c8ea01c483ad3d502644fff142b3c3
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .clangd
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. CPPLINT.cfg
  71. CRYPTO_OWNERS
  72. DEPS
  73. DIR_METADATA
  74. LICENSE
  75. LICENSE.chromium_os
  76. OWNERS
  77. PRESUBMIT.py
  78. PRESUBMIT_test.py
  79. PRESUBMIT_test_mocks.py
  80. README.md
  81. WATCHLISTS
README.md

Logo 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.