Re: libgomp: Compile-time error for non-portable gomp_mutex_t initialization

2015-11-19 Thread Jakub Jelinek
On Wed, Nov 18, 2015 at 06:19:29PM +0300, Ilya Verbin wrote: > On Fri, Sep 25, 2015 at 17:28:25 +0200, Jakub Jelinek wrote: > > On Fri, Sep 25, 2015 at 05:04:47PM +0200, Thomas Schwinge wrote: > > > On Thu, 26 Mar 2015 23:41:30 +0300, Ilya Verbin wrote: > > > > On Thu, Mar 26, 2015 at 13:09:19 +01

Re: libgomp: Compile-time error for non-portable gomp_mutex_t initialization

2015-11-18 Thread Ilya Verbin
On Fri, Sep 25, 2015 at 17:28:25 +0200, Jakub Jelinek wrote: > On Fri, Sep 25, 2015 at 05:04:47PM +0200, Thomas Schwinge wrote: > > On Thu, 26 Mar 2015 23:41:30 +0300, Ilya Verbin wrote: > > > On Thu, Mar 26, 2015 at 13:09:19 +0100, Jakub Jelinek wrote: > > > > the current code is majorly broken.

Re: libgomp: Compile-time error for non-portable gomp_mutex_t initialization (was: libgomp nvptx plugin: rework initialisation and support the proposed load/unload hooks)

2015-09-25 Thread Jakub Jelinek
On Fri, Sep 25, 2015 at 05:04:47PM +0200, Thomas Schwinge wrote: > Hi! > > It's Friday afternoon -- but anyway, is the following analysis correct? > > On Thu, 26 Mar 2015 23:41:30 +0300, Ilya Verbin wrote: > > On Thu, Mar 26, 2015 at 13:09:19 +0100, Jakub Jelinek wrote: > > > the current code is

libgomp: Compile-time error for non-portable gomp_mutex_t initialization (was: libgomp nvptx plugin: rework initialisation and support the proposed load/unload hooks)

2015-09-25 Thread Thomas Schwinge
, which is invoked from __attributed__((constructor)) functions generated by gcc/config/*/*mkoffload.c, and there is no guaranteed ordering for constructor functions [... -- see source code comment added in the following patch]: commit 81d25f393d9b0fdca309354e6a61f707ff403fe2 Author: Thomas Schwinge Date: Fri