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.

Sign up for GitHub

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

Jump to bottom

Ranges are not usable in device contexts #518

Closed
upsj opened this issue Apr 29, 2020 · 1 comment
Closed

Ranges are not usable in device contexts #518

upsj opened this issue Apr 29, 2020 · 1 comment
Labels
mod:cuda This is related to the CUDA module. mod:hip This is related to the HIP module.

Comments

@upsj
Copy link
Member

upsj commented Apr 29, 2020

The whole gko::range ecosystem doesn't work in device code, since it uses some __host__ functions and classes like std::forward, std::array, and after fixing that I can't seem to get the ROCm compiler to find the constructor for a gko::range<gko::accessor::row_major<ValueType, 2>> - my best guess is there are some issues with variadic templaces in device code.

Does anybody see a way to solve this (except for rewriting the whole range/accessor system?)
@upsj upsj added mod:cuda This is related to the CUDA module. mod:hip This is related to the HIP module. labels Apr 29, 2020
@upsj
Copy link
Member Author

upsj commented May 5, 2021

This seems to be no longer relevant, as we are now using ranges and accessors for mixed precision ELL #717

@upsj upsj closed this as completed May 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
mod:cuda This is related to the CUDA module. mod:hip This is related to the HIP module.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@upsj