public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Iain D Sandoe <iains@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc/devel/c++-coroutines] Merge master r12-1164.
Date: Wed, 2 Jun 2021 22:45:33 +0000 (GMT) [thread overview]
Message-ID: <20210602224533.8686D398544C@sourceware.org> (raw)
https://gcc.gnu.org/g:a7be5fecf1d22c2e7c07eb5289939928ba561b9c
commit a7be5fecf1d22c2e7c07eb5289939928ba561b9c
Merge: f25f21cea92 659cc7d6320
Author: Iain Sandoe <iain@sandoe.co.uk>
Date: Wed Jun 2 19:38:04 2021 +0100
Merge master r12-1164.
* Merge master r12-1164-g659cc7d6320.
Diff:
MAINTAINERS | 6 +
gcc/ChangeLog | 132 +++++++++++++++++++
gcc/DATESTAMP | 2 +-
gcc/c-family/ChangeLog | 9 ++
gcc/config/arc/arc.h | 2 +-
gcc/config/h8300/h8300-protos.h | 7 +-
gcc/config/h8300/h8300.c | 21 +--
gcc/config/h8300/h8300.md | 2 +
gcc/config/h8300/logical.md | 77 +++++------
gcc/config/h8300/shiftrotate.md | 12 +-
gcc/config/s390/s390.md | 14 +-
gcc/config/s390/subst.md | 2 +-
gcc/cp/ChangeLog | 19 +++
gcc/cp/init.c | 4 +-
gcc/fortran/ChangeLog | 38 ++++++
gcc/gimplify.c | 34 +----
gcc/ipa-icf.h | 2 +-
gcc/testsuite/ChangeLog | 61 +++++++++
gcc/testsuite/g++.dg/cpp0x/constexpr-delegating3.C | 10 ++
gcc/testsuite/g++.dg/cpp0x/dc10.C | 19 +++
gcc/testsuite/g++.dg/cpp0x/initlist-base4.C | 26 ++++
gcc/testsuite/g++.dg/cpp2a/constexpr-init22.C | 14 ++
gcc/testsuite/g++.dg/ext/builtin-shufflevector-1.C | 1 +
gcc/testsuite/gcc.dg/tree-ssa/tailcall-10.c | 12 ++
gcc/testsuite/gcc.dg/tree-ssa/tailcall-11.c | 12 ++
gcc/testsuite/gcc.dg/tree-ssa/tailcall-12.c | 12 ++
gcc/testsuite/gcc.dg/tree-ssa/tailcall-13.c | 15 +++
gcc/testsuite/gcc.dg/tree-ssa/tailrecursion-8.c | 11 ++
gcc/testsuite/gcc.target/s390/ashr.c | 11 ++
gcc/testsuite/gfortran.dg/gomp/taskloop-2.f90 | 72 +++++++++++
gcc/tree-ssa-phiopt.c | 144 ++++++---------------
gcc/tree-tailcall.c | 6 +-
libstdc++-v3/ChangeLog | 38 ++++++
libstdc++-v3/doc/html/manual/abi.html | 16 +--
libstdc++-v3/doc/html/manual/facets.html | 2 +-
libstdc++-v3/doc/html/manual/status.html | 18 +--
libstdc++-v3/doc/xml/manual/status_cxxis29124.xml | 6 +-
libstdc++-v3/doc/xml/manual/status_cxxtr1.xml | 6 +-
libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml | 7 +-
libstdc++-v3/include/bits/hashtable_policy.h | 6 +-
.../23_containers/deque/allocator/default_init.cc | 1 -
.../forward_list/allocator/default_init.cc | 1 -
.../23_containers/list/allocator/default_init.cc | 1 -
.../23_containers/map/allocator/default_init.cc | 1 -
.../23_containers/set/allocator/default_init.cc | 1 -
.../testsuite/23_containers/unordered_map/96088.cc | 22 +++-
.../unordered_map/allocator/default_init.cc | 1 -
.../testsuite/23_containers/unordered_set/96088.cc | 22 +++-
.../unordered_set/allocator/default_init.cc | 1 -
.../23_containers/vector/allocator/default_init.cc | 1 -
.../vector/bool/allocator/default_init.cc | 1 -
51 files changed, 695 insertions(+), 266 deletions(-)
reply other threads:[~2021-06-02 22:45 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=20210602224533.8686D398544C@sourceware.org \
--to=iains@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).