[go: nahoru, domu]

Roll libc++ from 6cd38f6d30dd to 0ad014cff450 (11 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libcxx.git/+log/6cd38f6d30dd..0ad014cff450

2023-11-29 koraq@xs4all.nl [libc++] Reenable codecvt in the dylib. (#73679)
2023-11-29 eric@efcs.ca Compile MSAN/TSAN failing test with -O1 (#73555)
2023-11-29 eric@efcs.ca [libc++] Remove linux Buildkite builders entirely (#73825)
2023-11-29 michael.platings@arm.com [libc++] Run picolibc tests with qemu
2023-11-29 koraq@xs4all.nl [libc++][format] Fixes formatting code units as integers. (#73396)
2023-11-29 michael.platings@arm.com [libc++] Add initial support for picolibc
2023-11-29 ldionne.2@gmail.com [libc++] Speed up classic locale (take 2) (#73533)
2023-11-29 ldionne.2@gmail.com [libc++] Build the dylib with sanitizers when requested (#73656)
2023-11-29 stl@nuwen.net [libc++] Remove unused Python imports (#73724)
2023-11-28 ldionne.2@gmail.com [libc++] Properly guard std::filesystem with >= C++17 (#72701)
2023-11-28 stl@nuwen.net [libc++][test] Change forbidden `extents<char>` to `extents<signed char>` (#73535)

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: Ia1264ad40bbe72d48a0000b307ff1868f732b1c1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5074480
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@{#1231058}
3 files changed
tree: 20819fea8ce2e2fd416c4303283a1781eb1acf17
  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. .gitattributes
  57. .gitignore
  58. .gitmodules
  59. .gn
  60. .mailmap
  61. .rustfmt.toml
  62. .vpython3
  63. .yapfignore
  64. ATL_OWNERS
  65. AUTHORS
  66. BUILD.gn
  67. CODE_OF_CONDUCT.md
  68. codereview.settings
  69. DEPS
  70. DIR_METADATA
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.