Displaying 4 results from an estimated 4 matches for "accel_device".
2011 Dec 13
0
[LLVMdev] Changes to the PTX calling conventions
...ojects like ocelot that have the device-only vs
> host/device differentiation. Maybe just device/host is good enough?*
>
Device/host just seems vague. Maybe we could create a set of specific
conventions, one set for OpenCL: cl_device/cl_kernel, and another set for
general accelerators, e.g. accel_device/accel_global.
> ****
>
> ****
>
> ****
>
> Thanks,****
>
> Micah****
>
> ****
>
> ****
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http...
2011 Dec 13
2
[LLVMdev] Changes to the PTX calling conventions
From: Justin Holewinski [mailto:justin.holewinski at gmail.com]
Sent: Tuesday, December 13, 2011 9:48 AM
To: Villmow, Micah
Cc: LLVM Developers Mailing List
Subject: Re: [LLVMdev] Changes to the PTX calling conventions
On Tue, Dec 13, 2011 at 11:25 AM, Villmow, Micah <Micah.Villmow at amd.com<mailto:Micah.Villmow at amd.com>> wrote:
Currently, PTX has its own calling conventions where
2011 Dec 13
3
[LLVMdev] Changes to the PTX calling conventions
...ong with projects like ocelot that have the device-only vs host/device differentiation. Maybe just device/host is good enough?
Device/host just seems vague. Maybe we could create a set of specific conventions, one set for OpenCL: cl_device/cl_kernel, and another set for general accelerators, e.g. accel_device/accel_global.
[Villmow, Micah] Yeah, that is true. What about leaving the calling convention alone for 'device' and just having a calling convention for 'kernel'(i.e. functions callable from another device). The normal calling conventions handle calls from the same device, but there...
2011 Dec 13
0
[LLVMdev] Changes to the PTX calling conventions
...evice-only vs
> host/device differentiation. Maybe just device/host is good enough?*****
>
> ** **
>
> Device/host just seems vague. Maybe we could create a set of specific
> conventions, one set for OpenCL: cl_device/cl_kernel, and another set for
> general accelerators, e.g. accel_device/accel_global.****
>
> *[Villmow, Micah] Yeah, that is true. What about leaving the calling
> convention alone for 'device' and just having a calling convention for
> 'kernel'(i.e. functions callable from another device). The normal calling
> conventions handle calls f...