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 branch 'releases/gcc-11' into devel/omp/gcc-11 Date: Tue, 18 May 2021 07:08:13 +0000 (GMT) [thread overview] Message-ID: <20210518070813.79FCF385782B@sourceware.org> (raw) https://gcc.gnu.org/g:23d1d32542202f28750b450cc550a0a78975d2f2 commit 23d1d32542202f28750b450cc550a0a78975d2f2 Merge: 6db84ecbd5f efb6bda7f51 Author: Tobias Burnus <tobias@codesourcery.com> Date: Tue May 18 09:06:34 2021 +0200 Merge branch 'releases/gcc-11' into devel/omp/gcc-11 Merge up to efb6bda7f5136d59be254b10d2b81ba28be8ecfb (May 18, 2021) Diff: contrib/ChangeLog | 9 +++ gcc/ChangeLog | 25 ++++++ gcc/DATESTAMP | 2 +- gcc/config/arm/arm.c | 26 +++++- gcc/config/arm/sync.md | 28 +++---- gcc/config/arm/thumb1.md | 15 ++++ gcc/configure | 3 +- gcc/configure.ac | 3 +- gcc/fortran/ChangeLog | 8 ++ gcc/fortran/resolve.c | 6 ++ gcc/testsuite/ChangeLog | 15 ++++ gcc/testsuite/gcc.target/arm/pr99977.c | 6 ++ gcc/testsuite/gfortran.dg/gomp/workshare-59.f90 | 26 ++++++ libgomp/ChangeLog | 9 +++ libstdc++-v3/ChangeLog | 28 +++++++ libstdc++-v3/include/bits/atomic_wait.h | 28 +++++-- libstdc++-v3/include/experimental/bits/fs_path.h | 2 +- .../27_io/filesystem/path/construct/100630.cc | 14 ++++ .../29_atomics/atomic/wait_notify/100334.cc | 93 ++++++++++++++++++++++ .../filesystem/path/construct/100630.cc | 14 ++++ 20 files changed, 330 insertions(+), 30 deletions(-)
next reply other threads:[~2021-05-18 7:08 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-18 7:08 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-17 10:33 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=20210518070813.79FCF385782B@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).