Re: C/C++ OpenACC: acc_pcopyin, acc_pcreate

2017-05-24 Thread Thomas Schwinge
Hi! On Wed, 24 May 2017 13:20:54 +0200, Jakub Jelinek wrote: > On Wed, May 24, 2017 at 12:55:27PM +0200, Thomas Schwinge wrote: > > On Tue, 23 May 2017 13:07:15 +0200, Jakub Jelinek wrote: > > > new symbols should never be added to an existing symbol > > > version after a GCC version with that s

Re: C/C++ OpenACC: acc_pcopyin, acc_pcreate

2017-05-24 Thread Jakub Jelinek
On Wed, May 24, 2017 at 12:55:27PM +0200, Thomas Schwinge wrote: > Hi Jakub! > > On Tue, 23 May 2017 13:07:15 +0200, Jakub Jelinek wrote: > > On Mon, May 22, 2017 at 04:26:48PM +0200, Thomas Schwinge wrote: > > > In , we currently describe acc_pcopyin, acc_pcreate as "old > > > names", but they'r

Re: C/C++ OpenACC: acc_pcopyin, acc_pcreate

2017-05-24 Thread Thomas Schwinge
Hi Jakub! On Tue, 23 May 2017 13:07:15 +0200, Jakub Jelinek wrote: > On Mon, May 22, 2017 at 04:26:48PM +0200, Thomas Schwinge wrote: > > In , we currently describe acc_pcopyin, acc_pcreate as "old > > names", but they're not "old" but really "alternative names", with the > > intention to provide

Re: C/C++ OpenACC: acc_pcopyin, acc_pcreate

2017-05-23 Thread Jakub Jelinek
On Mon, May 22, 2017 at 04:26:48PM +0200, Thomas Schwinge wrote: > In , we currently describe acc_pcopyin, acc_pcreate as "old > names", but they're not "old" but really "alternative names", with the > intention to provide them at symbol level, not via "#define"s. OK for > trunk? No. >