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

Rewrite calls to eg. Base.sin #112

Closed
maleadt opened this issue Jan 16, 2017 · 4 comments · Fixed by #151 · May be fixed by JuliaGPU/CUDAnative.jl#334
Closed

Rewrite calls to eg. Base.sin #112

maleadt opened this issue Jan 16, 2017 · 4 comments · Fixed by #151 · May be fixed by JuliaGPU/CUDAnative.jl#334

Comments

@maleadt
Copy link
Member

maleadt commented Jan 16, 2017

We should figure out a way to support users calling Base.sin instead of CUDAnative.sin. One possible option would be to hook inference, overriding method calls when operating under @cuda. The same mechanism could be used to dispatch on the hardware generation.

@maleadt
Copy link
Member Author

maleadt commented Jun 1, 2017

xref JuliaGPU/CUDAnative.jl#61

@maleadt maleadt transferred this issue from JuliaGPU/CUDAnative.jl May 27, 2020
@cdsousa
Copy link

cdsousa commented Nov 9, 2020

Any hope this can be sorted out in the near future? This issue is preventing me from using third-party libraries that I guess would work perfectly fine in CUDA.jl.
(edit: wrong example given, see next comment) For example, I'm calling some function of a library with a StaticArrays vector as an argument, and that function internally calls a normalize function that uses sqrt. I don't see how can I work around this.

@cdsousa
Copy link

cdsousa commented Nov 9, 2020

Sorry, my bad. I see that it actually works, I was getting another problem but thinking it was this one!
Anyway, there is still a problem with sin giving a warning.

@maleadt
Copy link
Member Author

maleadt commented Nov 9, 2020

Hopefully the new compiler interfaces in 1.6 will make this possible, yes. But still months away at the least.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants