This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgomp/52303] libgomp leaves threads lying around that cause trouble if the program is later fork()'d
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 19 Feb 2012 18:01:58 +0000
- Subject: [Bug libgomp/52303] libgomp leaves threads lying around that cause trouble if the program is later fork()'d
- Auto-submitted: auto-generated
- References: <bug-52303-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52303
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-02-19 18:01:58 UTC ---
Preserving the threads after the parallel region finishes is basically required
by the standard, as a new parallel region with the same number of threads needs
to preserve threadprivate data. So even after a parallel region is left, your
process is still multi-threaded.