[go: nahoru, domu]

Roll libc++ from e07dcc1eaa7e to bbce3ebce8ae (11 revisions)

https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libcxx.git/+log/e07dcc1eaa7e..bbce3ebce8ae

2023-10-12 ldionne.2@gmail.com [libc++] Check formatting with clang-format 17 (#68928)
2023-10-12 crtrott@sandia.gov [libc++][mdspan] Fix extents CTAD (#68737)
2023-10-12 ldionne.2@gmail.com [libc++] Improve the output of the generated-output CI job (#68903)
2023-10-12 zhangyin2018@iscas.ac.cn [libcxx] <experimental/simd> Add generate constructor of class simd (#66737)
2023-10-11 martin@martin.st [libcxx] [docs] Update the MinGW build example (#68790)
2023-10-11 martin@martin.st [libcxx] [docs] Remove mention of a MSVC/Debug mode caveat (#68791)
2023-10-11 ldionne.2@gmail.com [libc++] Run clang-format on newly-added test to fix CI
2023-10-11 ldionne.2@gmail.com [libc++][NFC] Fix typo in synopsis comment
2023-10-10 jyknight@google.com [libcxx] Allow string to use SSO in constant evaluation. (#66576)
2023-10-10 var-const@users.noreply.github.com [libc++][hardening] Undeprecate safe mode (#68391)
2023-10-10 ldionne.2@gmail.com [libc++] Remove libc++'s own <limits.h> (#65472)

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: Iaaea88b2b4d989cebed49639419909a3a68ae895
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4937421
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@{#1209135}
3 files changed
tree: 1c3da6b26e79b67d38deeb2e3e77c4ab82fd1048
  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. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gitmodules
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython3
  62. .yapfignore
  63. ATL_OWNERS
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. 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.