an opencl binding - zcl/panama

[Michael Zucchi]

On 26/1/20 2:19 pm, Ty Young wrote:
> On 1/24/20 5:23 AM, Maurizio Cimadamore wrote:
>> Thanks for putting the time on doing the conversion work (bleeding 
>> bonus point since we're in such an early stages) - and more 
>> importantly, for writing all the feedback up. I will be reading that 
>> carefully (and post some comments in here).
>>
>> This is what contributing looks like, kudos.
>
>
> Excuse me?
>
>
> I didn't realize your definition of "contributing" was literally 
> creating native libraries from C - something you yourselves could and 
> probably will do internally. I'm sorry, I guess? I've been speaking up 
> for myself for the most part. There isn't a whole lot of information 
> on what's going on with the project nor is the API itself feature 
> complete. If I knew you wanted someone to do native API compatibility 
> testing for you rather then comment on Memory Access API decisions I 
> probably would have to begin with. I didn't realize as someone who has 
> to use the API I couldn't do that. As someone else mentioned, adding 
> all this to the JEP would be nice. 

I dunno mate, I was a bit abrasive a few times so I think I deserved a 
bit of an underhanded comment about that behaviour and i'm pretty sure 
that was just directed at me.  The oracle devs have been very patient 
and thorough throughout - not something I could say about some other 
projects i've tried to become involved with lately whose list members 
were often rude or dismissive.

I'm not sure what you mean about "literally creating native libraries 
from C"?  There is no C involved.  I didn't re-implement libOpenCL.so.  
Being able to call a shared library function is the point of the work 
(or at least the one i have any interest in). They don't have infinite 
resources or might have a different view on things (as you do) so I 
would think external input can help make a better product.