Re: [PATCH 1/3, libgomp] Resolve libgomp plugin deadlock on exit, libgomp proper parts

2016-01-22 Thread Jakub Jelinek
On Tue, Jan 19, 2016 at 03:02:48PM +0900, Chung-Lin Tang wrote: > Ping x 2. I like the general idea of moving the gomp_fatal stuff up, out of the plugins, but we now have another plugin, so it can't apply as is. And in the intelmic plugin, adding return true; after abort (); looks wrong. So, can y

Re: [PATCH 1/3, libgomp] Resolve libgomp plugin deadlock on exit, libgomp proper parts

2016-01-18 Thread Chung-Lin Tang
Ping x 2. On 2016/1/5 11:22 PM, Chung-Lin Tang wrote: > Patch has been updated to accommodate the gomp_fini_device() removal changes. > And ping. > > On 2015/12/14 11:47 PM, Chung-Lin Tang wrote: >> [sorry, forgot to C gcc-patches in last send] >> >> Hi Jakub, >> these patches are a revision of

Re: [PATCH 1/3, libgomp] Resolve libgomp plugin deadlock on exit, libgomp proper parts

2016-01-05 Thread Chung-Lin Tang
Patch has been updated to accommodate the gomp_fini_device() removal changes. And ping. On 2015/12/14 11:47 PM, Chung-Lin Tang wrote: > [sorry, forgot to C gcc-patches in last send] > > Hi Jakub, > these patches are a revision of > https://gcc.gnu.org/ml/gcc-patches/2015-08/msg01701.html > since

[PATCH 1/3, libgomp] Resolve libgomp plugin deadlock on exit, libgomp proper parts

2015-12-14 Thread Chung-Lin Tang
[sorry, forgot to C gcc-patches in last send] Hi Jakub, these patches are a revision of https://gcc.gnu.org/ml/gcc-patches/2015-08/msg01701.html since that patch set have bitrotten by now. To recap the original situation, due to the way that device locks are held when entering plugin code, a GOM