Re: Implementing OpenACC's Fortran module

2014-09-22 Thread Tobias Burnus
On 22.09.2014 17:31, Tobias Burnus wrote: In case of OpenACC, the OpenACC semantics require that the argument is contiguous. If users gets it wrong, it will be wrong either way: If the variable is not packed and when it is packed (and the temporary removed after the function call). Post scrip

Re: Implementing OpenACC's Fortran module

2014-09-22 Thread Tobias Burnus
On 22.09.2014 17:17, Thomas Schwinge wrote: That works. For avoidance of doubt: just tag to the actual implementation (which is enough to avoid the references to _gfortran_internal_unpack and _gfortran_internal_pack), or also the interfaces, as detailed in the following "pseudo patch": Well, t

Re: Implementing OpenACC's Fortran module

2014-09-22 Thread Thomas Schwinge
Hi Tobias! On Sat, 20 Sep 2014 13:51:58 +0200, Tobias Burnus wrote: > On 19.09.2014 11:03, Thomas Schwinge wrote: > > Regarding linking the object file produced by Fortran openacc.f90 into > > libgomp: (with the version that Jim already has internally checked in) > > I find that libgomp then ha

Re: Implementing OpenACC's Fortran module

2014-09-20 Thread Tobias Burnus
On 19.09.2014 11:03, Thomas Schwinge wrote: Regarding linking the object file produced by Fortran openacc.f90 into libgomp: (with the version that Jim already has internally checked in) I find that libgomp then has undefined references to _gfortran_internal_unpack and _gfortran_internal_pack.

Re: Implementing OpenACC's Fortran module

2014-09-19 Thread Thomas Schwinge
Hi! On Wed, 20 Aug 2014 00:57:53 +0200, I wrote: > On Wed, 20 Aug 2014 00:05:22 +0200, Tobias Burnus wrote: > > James Norris wrote: > > > I think the files are ready for upstream submitting unless you can > > > think of other things > > > that should done. Yes? No? > > > > What do you mean by u