Open roflmaostc opened 1 year ago
I think it's just a problem with displaying things. The actual fftshift
method shouldn't call getindex
. Might be worth to inquire over at CUDA.jl as to whether there's a way for array wrappers to avoid this warning when displaying the array.
Overloading the display can be done. However the real problem is that all broadcasting operations fall back on get_index()
calls. This causes CUDA.jl
, depending on the settings to either fail or be really slow.
A sensible solution would be to implement broadcasting rules for ShiftedArrays
. Ideally these rules would be able to broadcast between arrays of the same shifts, of different shifts and between other AbstractArrays. For a circshifted array one probably needs to calculate intersection points and split the arrays into seperate parts. What do you think? Who knows how to implement proper broadcasting rules?
Hi,
how can we add CUDA support for this?
Best,
Felix