public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/redhat/heads/gcc-11-branch)] Merge commit 'r11-9920-gd26c3e4f733fcb07d90680491dd1d7a9d08c4705' into redhat/gcc-11-branch Date: Thu, 21 Apr 2022 12:40:35 +0000 (GMT) [thread overview] Message-ID: <20220421124035.EF7E538A284E@sourceware.org> (raw) https://gcc.gnu.org/g:1d3172725999deb0dca93ac70393ed9a0ad0da3f commit 1d3172725999deb0dca93ac70393ed9a0ad0da3f Merge: 46deeb7fcf0 d26c3e4f733 Author: Jakub Jelinek <jakub@redhat.com> Date: Thu Apr 21 14:40:21 2022 +0200 Merge commit 'r11-9920-gd26c3e4f733fcb07d90680491dd1d7a9d08c4705' into redhat/gcc-11-branch Diff: libstdc++-v3/config.h.in | 3 ++ libstdc++-v3/configure | 11 +++++ libstdc++-v3/configure.ac | 1 + libstdc++-v3/doc/html/manual/setup.html | 33 ++++++++++++++ libstdc++-v3/doc/xml/manual/intro.xml | 2 +- libstdc++-v3/doc/xml/manual/prerequisites.xml | 50 ++++++++++++++++++++++ libstdc++-v3/include/bits/forward_list.tcc | 5 +++ libstdc++-v3/include/bits/locale_facets_nonio.tcc | 27 ++++++------ libstdc++-v3/include/bits/ranges_base.h | 15 ++++--- libstdc++-v3/include/bits/regex_compiler.tcc | 4 +- libstdc++-v3/include/bits/stl_construct.h | 4 +- libstdc++-v3/include/bits/stl_deque.h | 7 +-- libstdc++-v3/include/experimental/internet | 10 +++-- libstdc++-v3/include/std/charconv | 11 +++-- libstdc++-v3/include/std/ranges | 2 +- libstdc++-v3/include/std/span | 6 +-- libstdc++-v3/src/Makefile.am | 4 +- libstdc++-v3/src/Makefile.in | 4 +- libstdc++-v3/src/c++11/cxx11-ios_failure.cc | 25 ++++++----- libstdc++-v3/src/c++11/future.cc | 26 ++++++----- libstdc++-v3/src/c++17/floating_from_chars.cc | 1 - libstdc++-v3/src/c++17/fs_ops.cc | 31 +++----------- libstdc++-v3/src/c++17/fs_path.cc | 5 --- libstdc++-v3/src/c++20/sstream-inst.cc | 4 +- libstdc++-v3/src/filesystem/ops-common.h | 40 +++++++++++++++++ libstdc++-v3/src/filesystem/ops.cc | 32 +++----------- libstdc++-v3/src/filesystem/path.cc | 31 ++++++++------ libstdc++-v3/testsuite/17_intro/names.cc | 4 ++ libstdc++-v3/testsuite/20_util/allocator/void.cc | 15 +++++++ .../testsuite/20_util/from_chars/pr105324.cc | 14 ++++++ .../21_strings/basic_string/cons/char/moveable.cc | 4 +- .../21_strings/basic_string/cons/char/moveable2.cc | 4 +- .../basic_string/cons/char/moveable2_c++17.cc | 4 +- .../basic_string/cons/wchar_t/moveable.cc | 4 +- .../basic_string/cons/wchar_t/moveable2.cc | 4 +- .../basic_string/cons/wchar_t/moveable2_c++17.cc | 4 +- .../basic_string/modifiers/assign/char/87749.cc | 2 +- .../basic_string/modifiers/assign/wchar_t/87749.cc | 2 +- .../operations/copy/char/constexpr.cc | 2 +- .../23_containers/forward_list/operations/merge.cc | 48 +++++++++++++++++++++ .../range_operations/advance_overflow.cc | 37 ++++++++++++++++ .../filesystem/operations/temp_directory_path.cc | 7 +++ .../filesystem/operations/temp_directory_path.cc | 9 +++- libstdc++-v3/testsuite/ext/rope/pthread7-rope.cc | 3 +- 44 files changed, 413 insertions(+), 148 deletions(-)
reply other threads:[~2022-04-21 12:40 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220421124035.EF7E538A284E@sourceware.org \ --to=jakub@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).