public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "olivier.grisel at ensta dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/52303] libgomp leaves threads lying around that cause trouble if the program is later fork()'d Date: Thu, 05 Sep 2013 09:47:00 -0000 [thread overview] Message-ID: <bug-52303-4-gV8WjSJwXy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52303-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52303 Olivier Grisel <olivier.grisel at ensta dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |olivier.grisel at ensta dot org --- Comment #4 from Olivier Grisel <olivier.grisel at ensta dot org> --- Wouldn't it be possible to make the libgomp runtime record the pid of the process who initialized the openmp thread pool and then whenever a parallel section is reached by the process to check whether the pid of the current process matches the pid that initialized the thread pool? If not a new init could be triggered at that point to make it possible to have a fork-child process use openmp sections in turn transparently. Alternatively it would be nice to have access to a public function to shutdown ("de-initialize") a thread pool prior to a fork.
next prev parent reply other threads:[~2013-09-05 9:47 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-18 0:34 [Bug libgomp/52303] New: " sdh4 at iastate dot edu 2012-02-18 10:05 ` [Bug libgomp/52303] " jakub at gcc dot gnu.org 2012-02-18 23:19 ` sdh4 at iastate dot edu 2012-02-19 18:50 ` jakub at gcc dot gnu.org 2013-09-05 9:47 ` olivier.grisel at ensta dot org [this message] 2013-09-05 10:06 ` olivier.grisel at ensta dot 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-52303-4-gV8WjSJwXy@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).