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
Subject: [gcc/devel/omp/gcc-11] Merge branch 'releases/gcc-11' into devel/omp/gcc-11
Date: Mon, 17 May 2021 10:33:33 +0000 (GMT) [thread overview]
Message-ID: <20210517103333.6B97A3857809@sourceware.org> (raw)
https://gcc.gnu.org/g:e9e03ca4b9fab1f3d711963581e71a8b747a5ad1
commit e9e03ca4b9fab1f3d711963581e71a8b747a5ad1
Merge: 17c55806b37 da1f3245a8f
Author: Tobias Burnus <tobias@codesourcery.com>
Date: Mon May 17 12:18:09 2021 +0200
Merge branch 'releases/gcc-11' into devel/omp/gcc-11
Merge up to da1f3245a8f0655b780c04d4f4cb0b96486547e4 (May 14, 2021).
Diff:
contrib/ChangeLog | 10 +
contrib/download_prerequisites | 2 +-
contrib/gcc-changelog/git_check_commit.py | 9 +-
contrib/gcc-changelog/git_commit.py | 43 ++-
contrib/gcc-changelog/git_email.py | 23 +-
contrib/gcc-changelog/git_repository.py | 7 +-
contrib/gcc-changelog/git_update_version.py | 9 +-
contrib/gcc-changelog/test_email.py | 23 +-
contrib/gcc-changelog/test_patches.txt | 430 ++++++++---------------
contrib/prerequisites.md5 | 2 +-
contrib/prerequisites.sha512 | 2 +-
gcc/ChangeLog | 38 ++
gcc/DATESTAMP | 2 +-
gcc/c-family/ChangeLog | 7 +
gcc/c-family/c.opt | 4 +-
gcc/c/ChangeLog | 5 +
gcc/fortran/resolve.c | 6 +-
gcc/testsuite/ChangeLog | 16 +
gcc/testsuite/g++.dg/cpp1y/pr88872.C | 24 ++
gcc/testsuite/gfortran.dg/gomp/implicit-save.f90 | 11 +
libgomp/ChangeLog | 8 +
libphobos/ChangeLog | 10 +
22 files changed, 357 insertions(+), 334 deletions(-)
next reply other threads:[~2021-05-17 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 10:33 Tobias Burnus [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-28 10:48 Tobias Burnus
2021-05-23 11:40 Tobias Burnus
2021-05-20 12:10 Tobias Burnus
2021-05-19 7:43 Tobias Burnus
2021-05-18 7:08 Tobias Burnus
2021-05-14 7:01 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=20210517103333.6B97A3857809@sourceware.org \
--to=burnus@gcc.gnu.org \
--cc=gcc-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).