Re: [gomp4] privatize internal array variables introduced by the fortran FE

2015-10-14 Thread Paul Richard Thomas
Dear Cesar, > > Is there any reason why only certain arrays have array descriptors? The > arrays with descriptors don't have this problem. It's only the ones > without descriptors that leak new internal variables that cause errors > with default(none). > This is an obvious question to which

[gomp4] privatize internal array variables introduced by the fortran FE

2015-10-13 Thread Cesar Philippidis
Arrays in fortran have a couple of internal variables associated with them, e.g. stride, lbound, ubound, size, etc. Depending on how and where the array was declared, these internal variables may be packed inside an array descriptor represented by a struct or defined individually. The major

Re: [gomp4] privatize internal array variables introduced by the fortran FE

2015-10-13 Thread Jakub Jelinek
On Tue, Oct 13, 2015 at 01:12:25PM -0700, Cesar Philippidis wrote: > Arrays in fortran have a couple of internal variables associated with > them, e.g. stride, lbound, ubound, size, etc. Depending on how and where > the array was declared, these internal variables may be packed inside an > array

Re: [gomp4] privatize internal array variables introduced by the fortran FE

2015-10-13 Thread Cesar Philippidis
On 10/13/2015 01:29 PM, Jakub Jelinek wrote: > On Tue, Oct 13, 2015 at 01:12:25PM -0700, Cesar Philippidis wrote: >> Arrays in fortran have a couple of internal variables associated with >> them, e.g. stride, lbound, ubound, size, etc. Depending on how and where >> the array was declared, these