-
Notifications
You must be signed in to change notification settings - Fork 6
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
Labels
Comments
Can you show me an example of what your doing (even better would be to
submit a unit test for us so we have something to fix if it turns out to be
legitimate).
…On Tue, Jun 5, 2018 at 3:01 PM, Laszlo32 ***@***.***> wrote:
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
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#11>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC5JAt7j4xwso7sDWG5Bsa-OPnid-WlDks5t5tWLgaJpZM4UbYYr>
.
|
Here is a quick Test Case EntryTest.txt |
@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
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
The text was updated successfully, but these errors were encountered: