public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/redhat/heads/gcc-11-branch)] Merge commit 'r11-8287-g7a7fc01b9d20afb1a2b805d93cb838a38e656420' into redhat/gcc-11-branch Date: Fri, 23 Apr 2021 18:16:00 +0000 (GMT) [thread overview] Message-ID: <20210423181600.D74253943431@sourceware.org> (raw) https://gcc.gnu.org/g:c76c301ee2291a548ade37778a77407e520967e5 commit c76c301ee2291a548ade37778a77407e520967e5 Merge: 8047c64ba5b 7a7fc01b9d2 Author: Jakub Jelinek <jakub@redhat.com> Date: Fri Apr 23 20:15:39 2021 +0200 Merge commit 'r11-8287-g7a7fc01b9d20afb1a2b805d93cb838a38e656420' into redhat/gcc-11-branch Diff: gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 17 ++++++++++ gcc/testsuite/{ => gfortran.dg}/substr_10.f90 | 0 gcc/testsuite/{ => gfortran.dg}/substr_9.f90 | 0 libgomp/ChangeLog | 8 +++++ libstdc++-v3/ChangeLog | 39 ++++++++++++++++++++++ libstdc++-v3/include/bits/atomic_timed_wait.h | 22 +++++++----- .../30_threads/semaphore/try_acquire_for.cc | 2 -- .../30_threads/semaphore/try_acquire_posix.cc | 1 + .../30_threads/semaphore/try_acquire_until.cc | 2 -- 10 files changed, 79 insertions(+), 14 deletions(-)
reply other threads:[~2021-04-23 18:16 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=20210423181600.D74253943431@sourceware.org \ --to=jakub@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).