From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-429008-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 10989 invoked by alias); 5 Sep 2013 09:47:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 10954 invoked by uid 48); 5 Sep 2013 09:47:22 -0000
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 4.6.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: olivier.grisel at ensta dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-52303-4-gV8WjSJwXy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-52303-4@http.gcc.gnu.org/bugzilla/>
References: <bug-52303-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-09/txt/msg00248.txt.bz2

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.