This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgomp/58378] Protect libgomp against child process hanging after a Unix fork()
- From: "olivier.grisel at ensta dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 10 Sep 2013 10:51:31 +0000
- Subject: [Bug libgomp/58378] Protect libgomp against child process hanging after a Unix fork()
- Auto-submitted: auto-generated
- References: <bug-58378-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58378
--- Comment #4 from Olivier Grisel <olivier.grisel at ensta dot org> ---
Thanks for the explanation. Would you consider a solution that would preserve
the state of the parent process and would just reset the thread pool data on
the child?
Otherwise we will have to consider that the way fork() is used in Python's
multiprocessing module is really an abuse and that there is no way to safely
use both openmp-libraries and Python multiprocessing in the same program
safely.