Re: PING – Re: [Patch, Fortran] -fcoarray=lib - support CRITICAL, prepare for locking support

2014-08-14 Thread Paul Richard Thomas
Dear Tobias, dear all, This patch and the documentation patch are OK for trunk. Many thanks Paul On 6 August 2014 08:46, Tobias Burnus wrote: > * PING * – of the patch with the obvious change mentioned by Alessandro > (i.e. using "if(is_lock_type)")? > > Tobias > > On 1 August 2014 21:57, Ale

Re: PING – Re: [Patch, Fortran] -fcoarray=lib - support CRITICAL, prepare for locking support

2014-08-12 Thread Tobias Burnus
*PING**2 Tobias PS: Now being back from vacation, I will try to review pending patches this evening. On 6 August 2014 08:46, Tobias Burnus wrote: * PING * – of the patch with the obvious change mentioned by Alessandro (i.e. using "if(is_lock_type)")? Tobias On 1 August 2014 21:57, Alessan

PING – Re: [Patch, Fortran] -fcoarray=lib - support CRITICAL, prepare for locking support

2014-08-05 Thread Tobias Burnus
* PING * – of the patch with the obvious change mentioned by Alessandro (i.e. using "if(is_lock_type)")? Tobias On 1 August 2014 21:57, Alessandro Fanfarillo wrote: Hello, I was implementing lock/unlock on the library side when I found a possible problem in the patch: if (is_lock_type == GFC

Re: [Patch, Fortran] -fcoarray=lib - support CRITICAL, prepare for locking support

2014-08-01 Thread Alessandro Fanfarillo
Hello, I was implementing lock/unlock on the library side when I found a possible problem in the patch: if (is_lock_type == GFC_CAF_CRITICAL) +reg_type = sym->attr.artificial ? GFC_CAF_CRITICAL : GFC_CAF_LOCK_STATIC; + else +reg_type = GFC_CAF_COARRAY_STATIC; the if statement cannot be

[Patch, Fortran] -fcoarray=lib - support CRITICAL, prepare for locking support

2014-07-28 Thread Tobias Burnus
This patch implements -fcoarray=lib support for CRITICAL blocks and includes some preparatory work for locking. In particular: * Updated the documentation for locking/critical, minor cleanup. The patch goes on top of the unreviewed patch https://gcc.gnu.org/ml/fortran/2014-07/msg00155.html *