On 09/18/2014 11:43 AM, Thomas Schwinge wrote:
> Hi Cesar!
>
> On Tue, 16 Sep 2014 17:32:54 -0700, Cesar Philippidis
> wrote:
>> The patch introduces the following OpenACC/PTX-specific built-ins:
>>
>> * GOACC_ntid
>> * GOACC_tid
>> * GOACC_nctaid
>> * GOACC_ctaid
>> * acc_on_device
>>
Hi Cesar!
On Tue, 16 Sep 2014 17:32:54 -0700, Cesar Philippidis
wrote:
> The patch introduces the following OpenACC/PTX-specific built-ins:
>
> * GOACC_ntid
> * GOACC_tid
> * GOACC_nctaid
> * GOACC_ctaid
> * acc_on_device
> * GOACC_get_thread_num
> * GOACC_get_num_threads
>
> Of
On 09/17/2014 01:49 AM, Jakub Jelinek wrote:
> On Wed, Sep 17, 2014 at 10:44:12AM +0200, Tobias Burnus wrote:
>> Cesar Philippidis wrote:
>>> The patch introduces the following OpenACC/PTX-specific built-ins:
>> ...
>>
>> It is not completely clear how they are supposed to get used. Should the
>> u
On Wed, Sep 17, 2014 at 10:44:12AM +0200, Tobias Burnus wrote:
> Cesar Philippidis wrote:
> > The patch introduces the following OpenACC/PTX-specific built-ins:
> ...
>
> It is not completely clear how they are supposed to get used. Should the
> user call them directly in some cases? Or are they o
Hi,
Cesar Philippidis wrote:
> The patch introduces the following OpenACC/PTX-specific built-ins:
...
It is not completely clear how they are supposed to get used. Should the
user call them directly in some cases? Or are they only used internally?
acc_on_device sounds like a function which would