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-11] Merge remote-tracking branch 'origin/releases/gcc-11' into devel/omp/gcc-11
Date: Fri, 4 Jun 2021 11:43:57 +0000 (GMT) [thread overview]
Message-ID: <20210604114357.DD3A2384841B@sourceware.org> (raw)
https://gcc.gnu.org/g:faf200a45c67a08d9cdcac9c307ce49f29aecfc0
commit faf200a45c67a08d9cdcac9c307ce49f29aecfc0
Merge: 8a0e7a2589d a8d93bf68a3
Author: Tobias Burnus <tobias@codesourcery.com>
Date: Fri Jun 4 12:42:30 2021 +0200
Merge remote-tracking branch 'origin/releases/gcc-11' into devel/omp/gcc-11
Merge up to a8d93bf68a3569047f91110b1c7e6c6c607b71aa (Jun 4, 2021)
Diff:
c++tools/ChangeLog | 8 +
gcc/ChangeLog | 82 +++++
gcc/DATESTAMP | 2 +-
gcc/ada/ChangeLog | 7 +
gcc/ada/gcc-interface/decl.c | 37 +-
gcc/config/arc/arc.h | 2 +-
gcc/config/arm/arm.md | 19 +-
gcc/config/i386/sse.md | 6 +-
gcc/cp/ChangeLog | 24 ++
gcc/cp/call.c | 26 +-
gcc/cp/init.c | 5 +-
gcc/range-op.cc | 11 +-
gcc/testsuite/ChangeLog | 89 +++++
gcc/testsuite/g++.dg/cpp2a/destroying-delete5.C | 36 ++
gcc/testsuite/g++.dg/inherit/virtual15.C | 18 +
gcc/testsuite/g++.dg/inherit/virtual15a.C | 19 ++
gcc/testsuite/gcc.target/arm/cmse/pr100333.c | 7 +
gcc/testsuite/gcc.target/powerpc/rop-5.c | 1 +
gcc/testsuite/gnat.dg/bit_packed_array6.adb | 10 +
gcc/testsuite/gnat.dg/bit_packed_array6_pkg.ads | 13 +
gcc/testsuite/gnat.dg/inline22.adb | 19 ++
gcc/testsuite/gnat.dg/specs/opt5.ads | 25 ++
gcc/testsuite/gnat.dg/specs/opt5_pkg.ads | 17 +
gcc/tree-inline.c | 15 +-
gcc/tree.h | 2 +-
libcpp/ChangeLog | 9 +
libstdc++-v3/ChangeLog | 67 ++++
libstdc++-v3/include/bits/c++config | 40 +--
libstdc++-v3/include/bits/ranges_base.h | 376 +++++++++++----------
libstdc++-v3/include/debug/macros.h | 4 +-
libstdc++-v3/python/Makefile.am | 4 +
libstdc++-v3/python/Makefile.in | 4 +
.../element_access/char/back_constexpr_neg.cc | 2 +-
.../element_access/char/constexpr_neg.cc | 2 +-
.../element_access/char/front_constexpr_neg.cc | 2 +-
.../element_access/wchar_t/back_constexpr_neg.cc | 2 +-
.../element_access/wchar_t/constexpr_neg.cc | 2 +-
.../element_access/wchar_t/front_constexpr_neg.cc | 2 +-
.../testsuite/23_containers/span/back_neg.cc | 2 +-
.../testsuite/23_containers/span/front_neg.cc | 2 +-
.../testsuite/23_containers/span/index_op_neg.cc | 2 +-
.../headers/iterator/synopsis_c++20.cc | 25 +-
.../24_iterators/range_operations/100768.cc | 128 +++++++
.../24_iterators/range_operations/advance.cc | 48 ++-
.../testsuite/std/ranges/adaptors/elements.cc | 3 +
.../testsuite/std/ranges/adaptors/transform.cc | 3 +
46 files changed, 928 insertions(+), 301 deletions(-)
next reply other threads:[~2021-06-04 11:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 11:43 Tobias Burnus [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-02 15:02 Tobias Burnus
2021-10-27 9:17 Tobias Burnus
2021-10-18 12:52 Tobias Burnus
2021-10-13 16:14 Tobias Burnus
2021-09-03 11:56 Tobias Burnus
2021-08-23 14:28 Tobias Burnus
2021-08-12 10:00 Tobias Burnus
2021-07-28 7:50 Tobias Burnus
2021-07-20 11:34 Tobias Burnus
2021-06-23 10:06 Tobias Burnus
2021-06-15 9:32 Tobias Burnus
2021-06-08 8:15 Tobias Burnus
2021-05-31 15:33 Tobias Burnus
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=20210604114357.DD3A2384841B@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: link
Be 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).