-
Notifications
You must be signed in to change notification settings - Fork 66
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
All kernels in the JNI should have hidden visibility #2168
All kernels in the JNI should have hidden visibility #2168
Conversation
Signed-off-by: Jihoon Son <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this work!
Signed-off-by: Jihoon Son <[email protected]>
build |
size_type num_rows, | ||
bool ansi_mode, | ||
bool strip) | ||
void CUDF_KERNEL string_to_integer_kernel(T* out, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be
void CUDF_KERNEL
or CUDF_KERNEL void
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Validity wise it doesn't matter. Stylistically it can be argued we should be consistent. I think it's outside the scope of this change to enforce it though. This example started with void __global__
and ended with void __global__ static
. This looks odd expanded out, but is valid and does the expected thing. I would prefer to see it as CUDF_KERNEL void
as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I was just replacing all __global__
with CUDF_KERNEL
and never noticed this. I agree CUDF_KERNEL void
is better and consistent. Will fix it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah just noticed it has been fixed already in #2178.
Fixes #1734.
This PR addresses a similar issue to rapidsai/cudf#14726. Instead of adding a new macro as suggested in #1734, it uses the one in libcudf added in rapidsai/cudf#14726 to avoid duplicate macros.