public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iii at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/98738] New: task-detach-6.f90 hangs intermittently Date: Mon, 18 Jan 2021 21:42:25 +0000 [thread overview] Message-ID: <bug-98738-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98738 Bug ID: 98738 Summary: task-detach-6.f90 hangs intermittently Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgomp Assignee: unassigned at gcc dot gnu.org Reporter: iii at linux dot ibm.com CC: jakub at gcc dot gnu.org Target Milestone: --- I'm currently on commit 2e43880dbd4c. Building task-detach-6.exe and running it in a loop eventually leads to a hang (might take a while, during the last run it happened after 7k runs): gcc/build/x86_64-pc-linux-gnu/libgomp/testsuite$ while true; do LD_LIBRARY_PATH=../../../../install/lib64 ./task-detach-6.exe; echo -n .; done I first spotted this on s390 and then checked on x86_64; the issue is reproducible on both.
next reply other threads:[~2021-01-18 21:42 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-18 21:42 iii at linux dot ibm.com [this message] 2021-01-18 21:50 ` [Bug libgomp/98738] " iii at linux dot ibm.com 2021-01-19 3:03 ` hjl.tools at gmail dot com 2021-01-19 8:51 ` dominiq at lps dot ens.fr 2021-01-19 10:35 ` ro at gcc dot gnu.org 2021-01-19 13:22 ` jakub at gcc dot gnu.org 2021-01-19 15:13 ` kcy at codesourcery dot com 2021-01-20 15:53 ` jakub at gcc dot gnu.org 2021-01-20 16:06 ` jakub at gcc dot gnu.org 2021-01-21 13:00 ` kcy at codesourcery dot com 2021-01-21 13:12 ` jakub at gcc dot gnu.org 2021-01-24 16:52 ` dominiq at lps dot ens.fr 2021-02-25 22:48 ` cvs-commit at gcc dot gnu.org 2021-03-11 13:58 ` tschwinge at gcc dot gnu.org 2021-03-11 14:03 ` jakub at gcc dot gnu.org 2021-03-11 14:05 ` kcy at codesourcery dot com 2021-03-11 14:30 ` tschwinge at gcc dot gnu.org 2021-03-11 16:37 ` tschwinge 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-05-29 10:04 ` 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-98738-4@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: 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).