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++/93456] No overflow check in __atomic_futex_unsigned_base::_M_futex_wait_until
Date: Mon, 16 Nov 2020 21:15:26 +0000 [thread overview]
Message-ID: <bug-93456-4-sV6eB0MMZb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93456-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93456
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:730e1357dfb9aff481d6c47a21ef748f0d810d4f
commit r10-9031-g730e1357dfb9aff481d6c47a21ef748f0d810d4f
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Fri Nov 13 19:11:02 2020 +0000
libstdc++: Remove redundant overflow check for futex timeout [PR 93456]
The relative_timespec function already checks for the case where the
specified timeout is in the past, so the difference can never be
negative. That means we dn't need to check if it's more negative than
the minimum time_t value.
libstdc++-v3/ChangeLog:
PR libstdc++/93456
* src/c++11/futex.cc (relative_timespec): Remove redundant check
negative values.
* testsuite/30_threads/future/members/93456.cc: New.
(cherry picked from commit b8d36dcc917e8a06d8c20b9f5ecc920ed2b9e947)
next prev parent reply other threads:[~2020-11-16 21:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-93456-4@http.gcc.gnu.org/bugzilla/>
2020-11-14 0:16 ` cvs-commit at gcc dot gnu.org
2020-11-14 0:25 ` redi at gcc dot gnu.org
2020-11-16 21:15 ` cvs-commit at gcc dot gnu.org [this message]
2020-11-19 13:33 ` cvs-commit at gcc dot gnu.org
2020-11-25 15:11 ` redi at gcc dot gnu.org
2020-12-29 13:12 ` aoliva at gcc dot gnu.org
2021-04-19 10:40 ` redi 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-93456-4-sV6eB0MMZb@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).