public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc/devel/omp/gcc-12] Merge branch 'releases/gcc-12' into devel/omp/gcc-12 Date: Fri, 25 Nov 2022 10:37:08 +0000 (GMT) [thread overview] Message-ID: <20221125103708.96A1C384E393@sourceware.org> (raw) https://gcc.gnu.org/g:cd2d5296d42226a69284a81eeea13638c9c98388 commit cd2d5296d42226a69284a81eeea13638c9c98388 Merge: a6f9d8c189e ed8d7ecac11 Author: Tobias Burnus <tobias@codesourcery.com> Date: Fri Nov 25 11:36:18 2022 +0100 Merge branch 'releases/gcc-12' into devel/omp/gcc-12 Merge up to r12-8941-ged8d7ecac11d587687986a0895050955c09d2f43 (25th Nov 2022) Diff: gcc/ChangeLog | 24 +++++ gcc/DATESTAMP | 2 +- gcc/range-op.cc | 3 + gcc/testsuite/ChangeLog | 9 ++ gcc/testsuite/gnat.dg/opt100.adb | 13 +++ gcc/testsuite/gnat.dg/opt100_pkg.adb | 17 ++++ gcc/testsuite/gnat.dg/opt100_pkg.ads | 23 +++++ gcc/testsuite/gnat.dg/sso18.adb | 21 ++++ gcc/tree-loop-distribution.cc | 7 +- libstdc++-v3/ChangeLog | 113 +++++++++++++++++++++ libstdc++-v3/doc/html/manual/bugs.html | 3 + libstdc++-v3/doc/xml/manual/intro.xml | 6 ++ libstdc++-v3/include/bits/chrono.h | 10 +- libstdc++-v3/include/bits/fs_dir.h | 33 ++++-- libstdc++-v3/include/bits/fs_path.h | 13 ++- libstdc++-v3/include/bits/iterator_concepts.h | 28 ++++- libstdc++-v3/include/bits/regex.h | 24 ++++- libstdc++-v3/include/experimental/bits/fs_path.h | 9 +- libstdc++-v3/include/std/barrier | 9 +- libstdc++-v3/include/std/expected | 9 +- libstdc++-v3/include/std/memory | 1 - libstdc++-v3/include/std/type_traits | 45 ++++---- libstdc++-v3/src/c++17/memory_resource.cc | 4 +- .../20_util/is_nothrow_convertible/value.cc | 2 - .../value_ext.cc => is_nothrow_invocable/91456.cc} | 19 ++-- libstdc++-v3/testsuite/20_util/tuple/swap.cc | 2 +- .../testsuite/26_numerics/valarray/87641.cc | 2 +- .../testsuite/27_io/filesystem/iterators/106201.cc | 14 +++ .../27_io/filesystem/iterators/lwg3719.cc | 39 +++++++ .../28_regex/iterators/regex_iterator/lwg3719.cc | 29 ++++++ .../iterators/regex_token_iterator/lwg3719.cc | 29 ++++++ .../experimental/filesystem/iterators/106201.cc | 14 +++ 32 files changed, 511 insertions(+), 65 deletions(-)
next reply other threads:[~2022-11-25 10:37 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-25 10:37 Tobias Burnus [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-02-27 16:34 Tobias Burnus 2023-02-20 6:52 Tobias Burnus 2023-02-13 9:21 Tobias Burnus 2023-02-06 7:42 Tobias Burnus 2023-01-19 20:24 Tobias Burnus 2023-01-09 9:21 Tobias Burnus 2022-12-27 10:54 Tobias Burnus 2022-12-21 18:21 Tobias Burnus 2022-12-19 17:32 Tobias Burnus 2022-11-18 9:48 Tobias Burnus 2022-11-14 15:41 Tobias Burnus 2022-10-24 10:21 Tobias Burnus 2022-10-11 8:26 Tobias Burnus 2022-09-29 14:45 Tobias Burnus 2022-09-23 8:48 Tobias Burnus 2022-09-09 13:39 Tobias Burnus 2022-08-31 6:14 Tobias Burnus 2022-07-28 13:29 Tobias Burnus 2022-07-28 13:29 Tobias Burnus 2022-07-01 18:13 Kwok Yeung
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=20221125103708.96A1C384E393@sourceware.org \ --to=burnus@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).