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

[BUG] Static builds of libcudf cause runtime failures due to public kernel symbols #14734

Closed
robertmaynard opened this issue Jan 10, 2024 · 2 comments
Assignees
Labels
bug Something isn't working Spark Functionality that helps Spark RAPIDS

Comments

@robertmaynard
Copy link
Contributor

Describe the bug
Downstream consumers of static built versions of libcudf such as spark have encountered runtime issues due to multiple instances of the same kernel existing in different DSOs.

This matches the issue detailed NVIDIA/cccl#166 where multiple DSO using CCCL run into issues at runtime.

Expected behavior
The expected behavior is that all libcudf kernels would have internal linkage and therefore not cause issues when being built statically.

This does mean that we will need CCCL and CuCo versions that also mark all CUDA kernels with internal linkage.

@robertmaynard robertmaynard added bug Something isn't working 2 - In Progress Currently a work in progress Spark Functionality that helps Spark RAPIDS labels Jan 10, 2024
@robertmaynard robertmaynard self-assigned this Jan 10, 2024
@robertmaynard
Copy link
Contributor Author

robertmaynard commented Jan 10, 2024

Task list:

@robertmaynard
Copy link
Contributor Author

Closing as all PR's have been merged into 24.02

@robertmaynard robertmaynard removed the 2 - In Progress Currently a work in progress label Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Spark Functionality that helps Spark RAPIDS
Projects
None yet
Development

No branches or pull requests

1 participant