public inbox for gcc-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: Mon, 31 May 2021 15:33:26 +0000 (GMT) [thread overview]
Message-ID: <20210531153326.644D3384F010@sourceware.org> (raw)
https://gcc.gnu.org/g:880b2839feaf759959844d91f89a55858185a964
commit 880b2839feaf759959844d91f89a55858185a964
Merge: b10e254b4c8 718a78fcfb0
Author: Tobias Burnus <tobias@codesourcery.com>
Date: Mon May 31 16:51:52 2021 +0200
Merge remote-tracking branch 'origin/releases/gcc-11' into devel/omp/gcc-11
Merged up to 718a78fcfb03ca3c552800b510ef3eb085bcbb76 (May 31, 2021)
Diff:
c++tools/server.cc | 1 +
gcc/ChangeLog | 12 +++
gcc/DATESTAMP | 2 +-
gcc/builtins.c | 2 +
gcc/calls.c | 3 +-
gcc/config/rs6000/aix.h | 2 +
gcc/config/rs6000/rs6000.c | 17 +++-
gcc/cp/ChangeLog | 9 ++
gcc/cp/call.c | 5 +-
gcc/cp/typeck.c | 10 ++
gcc/doc/tm.texi | 9 ++
gcc/doc/tm.texi.in | 2 +
gcc/fortran/ChangeLog | 28 +++++
gcc/fortran/trans-array.c | 5 +-
gcc/fortran/trans-decl.c | 1 +
gcc/fortran/trans-intrinsic.c | 9 +-
gcc/function.c | 3 +
gcc/regcprop.c | 49 ++++-----
gcc/target.def | 12 +++
gcc/testsuite/ChangeLog | 33 ++++++
gcc/testsuite/g++.dg/cpp1z/nodiscard8.C | 15 +++
gcc/testsuite/g++.dg/cpp1z/nodiscard9.C | 22 ++++
gcc/testsuite/g++.dg/other/pr100580.C | 8 ++
gcc/testsuite/g++.dg/template/access37.C | 26 +++++
gcc/testsuite/g++.dg/template/access37a.C | 6 ++
gcc/testsuite/gcc.c-torture/compile/pr100576.c | 12 +++
gcc/testsuite/gcc.dg/cpp/pr100646-1.c | 5 +
gcc/testsuite/gcc.dg/cpp/pr100646-2.c | 6 ++
gcc/testsuite/gcc.dg/pr100590.c | 13 +++
gcc/testsuite/gcc.target/i386/pr100342.c | 70 +++++++++++++
gcc/testsuite/gfortran.dg/bounds_check_22.f90 | 12 +++
gcc/testsuite/gfortran.dg/pointer_check_14.f90 | 28 +++++
gcc/testsuite/gfortran.dg/pr98411.f90 | 16 +++
libcpp/lex.c | 5 +-
libstdc++-v3/ChangeLog | 43 ++++++++
libstdc++-v3/include/std/ranges | 112 ++++++++++++++++----
libstdc++-v3/testsuite/lib/dg-options.exp | 47 ++++++++-
.../testsuite/std/ranges/adaptors/100479.cc | 113 +++++++++++++++++++++
libstdc++-v3/testsuite/std/ranges/adaptors/join.cc | 24 +++++
39 files changed, 741 insertions(+), 56 deletions(-)
next reply other threads:[~2021-05-31 15:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 15:33 Tobias Burnus [this message]
2021-06-04 11:43 Tobias Burnus
2021-06-08 8:15 Tobias Burnus
2021-06-15 9:32 Tobias Burnus
2021-06-23 10:06 Tobias Burnus
2021-06-28 10:32 Tobias Burnus
2021-07-20 11:34 Tobias Burnus
2021-07-23 8:36 Tobias Burnus
2021-07-28 7:50 Tobias Burnus
2021-07-30 9:53 Tobias Burnus
2021-08-09 7:10 Tobias Burnus
2021-08-12 10:00 Tobias Burnus
2021-08-16 12:08 Tobias Burnus
2021-08-23 14:28 Tobias Burnus
2021-09-03 11:56 Tobias Burnus
2021-09-06 13:31 Tobias Burnus
2021-09-13 7:46 Tobias Burnus
2021-09-17 13:46 Tobias Burnus
2021-09-20 7:42 Tobias Burnus
2021-09-20 15:34 Tobias Burnus
2021-09-22 8:37 Tobias Burnus
2021-09-28 10:05 Tobias Burnus
2021-10-06 11:01 Tobias Burnus
2021-10-11 11:15 Tobias Burnus
2021-10-13 16:14 Tobias Burnus
2021-10-18 12:52 Tobias Burnus
2021-10-19 13:39 Tobias Burnus
2021-10-19 13:39 Tobias Burnus
2021-10-27 9:17 Tobias Burnus
2021-11-02 15:02 Tobias Burnus
2021-11-10 14:34 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=20210531153326.644D3384F010@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).