Aaron Watry writes:
> Hi list,
>
> I was starting to look into getting cppamp-driver-ng working with
> mesa/clover, and I quickly ran into a question...
>
> cppamp-driver-ng explicitly lists which platforms are supported in its
> OpenCL back-end's source code. I went to add in the Mesa/Clover
> e
These are the platforms recognized by cppamp-driver-ng, and what I'd
need to add currently to get clover working on radeonsi (assuming we
supported all the necessary built-ins and also enabled the static
storage class specifier in clang successfully):
Label I've assigned: Vendor String / Platform
On Tue, Jul 29, 2014 at 09:50:23AM -0500, Aaron Watry wrote:
> Hi list,
>
> I was starting to look into getting cppamp-driver-ng working with
> mesa/clover, and I quickly ran into a question...
>
> cppamp-driver-ng explicitly lists which platforms are supported in its
> OpenCL back-end's source c
Hi list,
I was starting to look into getting cppamp-driver-ng working with
mesa/clover, and I quickly ran into a question...
cppamp-driver-ng explicitly lists which platforms are supported in its
OpenCL back-end's source code. I went to add in the Mesa/Clover
entries, and discovered that we're ac
