public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/101761] Random hang with 29_atomics/atomic_ref/wait_notify.cc
Date: Wed, 04 Aug 2021 15:50:03 +0000 [thread overview]
Message-ID: <bug-101761-4-RuQJc5jkoE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101761-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101761
--- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to H.J. Lu from comment #0)
> 29_atomics/atomic_ref/wait_notify.cc in 64-bit on Skylake server:
>
> It happens about once a few weeks.
while true ; do ./a.out ; done
will hang immediately.
next prev parent reply other threads:[~2021-08-04 15:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 18:30 [Bug target/101761] New: " hjl.tools at gmail dot com
2021-08-03 18:55 ` [Bug target/101761] " ubizjak at gmail dot com
2021-08-04 15:50 ` ubizjak at gmail dot com [this message]
2021-08-04 15:53 ` redi at gcc dot gnu.org
2021-09-08 1:04 ` rodgertq at gcc dot gnu.org
2021-09-15 8:56 ` fw at gcc dot gnu.org
2021-09-15 18:40 ` rodgertq at gcc dot gnu.org
2021-09-15 18:48 ` redi at gcc dot gnu.org
2021-09-15 18:50 ` fw at gcc dot gnu.org
2021-09-15 18:52 ` redi at gcc dot gnu.org
2021-09-15 18:54 ` redi at gcc dot gnu.org
2021-09-15 18:55 ` redi at gcc dot gnu.org
2021-09-15 18:56 ` rodgertq at gcc dot gnu.org
2021-09-16 19:04 ` redi at gcc dot gnu.org
2021-09-16 21:48 ` cvs-commit at gcc dot gnu.org
2021-10-06 23:41 ` hjl.tools at gmail dot com
2021-10-07 6:45 ` redi at gcc dot gnu.org
2021-10-12 10:59 ` cvs-commit at gcc dot gnu.org
2022-12-28 20:08 ` [Bug testsuite/101761] " pinskia 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-101761-4-RuQJc5jkoE@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).