-
Notifications
You must be signed in to change notification settings - Fork 64
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
Cannot use <limits>
and <cuda/std/limits>
in the same source file
#107
Comments
@benbarsdell this is the same issue I reported a while ago. Did you have a chance to think about how to fix this? |
I'll see if I can take another look at this later this week. |
@benbarsdell Hi, any updates on this? I'm reviewing rapidsai/cudf#11287 and would like to understand the issue / what solutions might be possible. |
I believe the root cause of this is the The solution will be to distinguish between Unfortunately this is easier said than done, which is why I haven't got to it yet. In terms of workarounds, removing |
This PR enables using [upstream jitify2](https://github.com/NVIDIA/jitify/tree/jitify2) rather than RAPIDS' fork of [jitify2](https://github.com/rapidsai/jitify/tree/cudf_0.19). This enables us to take advantage of the latest additions/improvements to jitify. Most notably: upstream jitify2 dlsym/dlopens `libcuda.so` which enables us to [drop our shared library dependency on `libcuda.so`](#11370). --- Two major issues came up when making the switch: 1. NVIDIA/jitify#107 - I used the workaround mentioned in that issue. Hopefully it is fixed soon and we can eliminate the workaround. 2. We need to pass `-D_FILE_OFFSET_BITS=64` to jitify. Due to limitations in the way conda-forge builds glibc, we must explicitly state we require 64bit file offset support. Authors: - Ashwin Srinath (https://github.com/shwina) Approvers: - Yunsong Wang (https://github.com/PointKernel) - Bradley Dice (https://github.com/bdice) - Robert Maynard (https://github.com/robertmaynard) URL: #11287
Invoking jitify with the following source file:
as follows:
results in:
As a workaround I can do:
The text was updated successfully, but these errors were encountered: