public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/109664] New: Deadlocks with gomp_fatal called from libgomp/plugins/ Date: Fri, 28 Apr 2023 10:06:02 +0000 [thread overview] Message-ID: <bug-109664-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109664 Bug ID: 109664 Summary: Deadlocks with gomp_fatal called from libgomp/plugins/ Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgomp Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: jakub at gcc dot gnu.org Target Milestone: --- See thread starting at: https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603616.html Issue: Fatal errors inside mutex-locked regions (i.e. basically anything in the plugin) will cause it to hang up trying to take the lock to clean everything up. Possible solutions: would be not use gomp_fatal from within the plugins, but use gomp_error instead and through possibly adjusted plugin APIs tell libgomp that there was a fatal error and let libgomp unlock anything that needs unlocking and exit (EXIT_FAILURE); afterwards. another possibility would be not use gomp_fatal from within the plugins, but use gomp_error instead and through possibly adjusted plugin APIs tell libgomp that there was a fatal error and let libgomp unlock anything that needs unlocking and exit (EXIT_FAILURE); afterwards.
next reply other threads:[~2023-04-28 10:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-28 10:06 burnus at gcc dot gnu.org [this message] 2023-04-28 10:45 ` [Bug libgomp/109664] " burnus 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-109664-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).