Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compile OpenCL entry-point #11

Open
Laszlo32 opened this issue Jun 5, 2018 · 3 comments
Open

Compile OpenCL entry-point #11

Laszlo32 opened this issue Jun 5, 2018 · 3 comments
Labels

Comments

@Laszlo32
Copy link

Laszlo32 commented Jun 5, 2018

Hi,

there is a strange behaviour when trying to execute a kernel with an entry point other than "run":

On the java-side the entry-point is checked fine, and the OpenCL source is generated for the custom entry-point.
But when trying to compile it in com.aparapi.internal.kernel.KernelRunner.java:1543 the custom entry-point is not given to the native call.
And in aparapi-native/src/cpp/runKernel/Aparapi.cpp : 1338 the kernel seams to be compiled with the "run" entry-point which fails for obvious reasons as there is no "run" method in the OpenCL source.

Afterwards this whole generating + compilation is tried for the next candidate (the CPU) which also fails.

I would have tried to change in Aparapi.cpp : 1338 "run" to the custom entry-point but was not able to compile to verify if this would be enough.

kind regards

@freemo
Copy link
Member

freemo commented Jun 5, 2018 via email

@Laszlo32
Copy link
Author

Laszlo32 commented Jun 5, 2018

Here is a quick Test Case

EntryTest.txt
had to change the extension from .java to .txt

@freemo freemo added the bug label Jun 6, 2018
@freemo
Copy link
Member

freemo commented Jun 6, 2018

@Laszlo32 thanks I'll look into it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants