public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/98678] 30_threads/future/members/poll.cc execution test FAILs
Date: Thu, 14 Jan 2021 12:59:27 +0000 [thread overview]
Message-ID: <bug-98678-4-0vNsiGpPZt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98678-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98678
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2021-01-14
Status|UNCONFIRMED |NEW
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The relevant part of the std::future code on the gcc-10 branch is very
different, so the timings are different on the branch too.
This test is a bit tricky. The whole point is to check that performance of one
operation is acceptable compared to a baseline. But the definition of
"acceptable" and the relative difference between the speed of the different
operations varies with arch. We could just increase the tolerances, but then we
allow worse performance on the targets that don't need it. Maybe we want to
change the 30 and 100 magic numbers to depend on the target.
next prev parent reply other threads:[~2021-01-14 12:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 12:16 [Bug libstdc++/98678] New: " ro at gcc dot gnu.org
2021-01-14 12:17 ` [Bug libstdc++/98678] " ro at gcc dot gnu.org
2021-01-14 12:59 ` redi at gcc dot gnu.org [this message]
2021-04-19 21:27 ` seurer at gcc dot gnu.org
2021-04-27 11:40 ` jakub at gcc dot gnu.org
2021-07-28 7:05 ` rguenth at gcc dot gnu.org
2022-04-21 7:48 ` rguenth at gcc dot gnu.org
2023-04-05 16:51 ` danglin at gcc dot gnu.org
2023-05-29 10:03 ` jakub 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-98678-4-0vNsiGpPZt@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).