public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/98738] task-detach-6.f90 hangs intermittently Date: Thu, 11 Mar 2021 13:58:53 +0000 [thread overview] Message-ID: <bug-98738-4-T1eH9WI7D0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98738-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98738 Thomas Schwinge <tschwinge at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tschwinge at gcc dot gnu.org Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |kcy at codesourcery dot com --- Comment #13 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- Kwok, it seems -- at least in my testing -- that your latest commit d656bfda2d8316627d0bbb18b10954e6aaf3c88c "openmp: Fix intermittent hanging of task-detach-6 libgomp tests [PR98738]" has broken things with nvptx offloading enabled: because of hanging 'libgomp.c/../libgomp.c-c++-common/task-detach-6.c', I manually terminated testing after: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 24507 thomas 20 0 9157400 130444 122980 R 100.0 0.4 41:13.59 ./task-detach-6.exe ..., and another run after: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 32365 thomas 20 0 9159472 140040 128136 R 100.0 0.4 59:05.48 ./task-detach-6.exe I had 100 % GPU utilization in this state. Is there something wrong (are you or anyone reproducing that with nvptx offloading?), or is something wrong on my side?
next prev parent reply other threads:[~2021-03-11 13:58 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-18 21:42 [Bug libgomp/98738] New: " iii at linux dot ibm.com 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 [this message] 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-T1eH9WI7D0@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).