public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/102074] include/bits/atomic_timed_wait.h:215: possible missing return ?
Date: Tue, 31 Aug 2021 16:46:56 +0000	[thread overview]
Message-ID: <bug-102074-4-wPKynoKxCy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102074-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102074

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:763eb1f19239ebb19c0f87590a4f02300c02c52b

commit r12-3263-g763eb1f19239ebb19c0f87590a4f02300c02c52b
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Aug 31 16:50:17 2021 +0100

    libstdc++: Add missing return for atomic timed wait [PR102074]

    This adds a missing return statement to the non-futex wait-until
    operation.

    Signed-off-by: Jonathan Wakely <jwakely@redhat.com>

    libstdc++-v3/ChangeLog:

            PR libstdc++/102074
            * include/bits/atomic_timed_wait.h (__timed_waiter_pool)
            [!_GLIBCXX_HAVE_PLATFORM_TIMED_WAIT]: Add missing return.

  parent reply	other threads:[~2021-08-31 16:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26  9:19 [Bug libstdc++/102074] New: " dcb314 at hotmail dot com
2021-08-26 12:16 ` [Bug libstdc++/102074] " redi at gcc dot gnu.org
2021-08-28 10:19 ` redi at gcc dot gnu.org
2021-08-31 16:46 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-12 10:58 ` cvs-commit at gcc dot gnu.org
2022-01-16  1:16 ` rodgertq at gcc dot gnu.org

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=bug-102074-4-wPKynoKxCy@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).