bump compat to GPUArrays v11, JLArrays v0.2, KernelAbstractions 0.9

[milankl]

No description provided.

[milankl]

@jackleland @maximilian-gelbrecht I believe we can now upgrade GPUArrays, JLArrays, and KernelAbstractions compat.

One would (fingers crossed) roll forward these two changes again

SpeedyWeather.jl/src/RingGrids/general.jl

Lines 485 to 489 in f90b9d8

	function KernelAbstractions.get_backend(
	g::Grid
	) where {Grid <: AbstractGridArray{T, N, ArrayType}} where {T, N, ArrayType <: GPUArrays.AbstractGPUArray}
	return KernelAbstractions.get_backend(g.data)
	end

SpeedyWeather.jl/src/LowerTriangularMatrices/lower_triangular_array.jl

Lines 633 to 637 in 719dce9

	function KernelAbstractions.get_backend(
	a::LowerTriangularArray{T, N, ArrayType}
	) where {T, N, ArrayType <: GPUArrays.AbstractGPUArray}
	return KernelAbstractions.get_backend(a.data)
	end

that #636 rolled back

[maximilian-gelbrecht]

Tests are passing here. I'd like to briefly test on GPU before merging as well.

[maximilian-gelbrecht]

Ah, the tests are passing here, but I think the compat entries are actually wrong, we do loose compatibility with GPUArrays v10. It'll be only compatible with v11.

[milankl]

riiiight, is there a reason why we wouldn't upgrade then? E.g. I guess this means that older CUDA jl versions don't support v11, does that restrict us in any other way?

[maximilian-gelbrecht]

I mean it's only relevant if someone wants to use Speedy with some package that isn't updated yet to be compatible with GPUArrays v11. Not sure if there are many around. This is only relevant for packages that do something with GPUs. Even if that's the case, they'd still just get a slightly older version of Speedy.

[milankl]

Oceananigans still uses GPUArrays v10, so at the moment that would disallow running both simultaneously (coupling), but I believe by the time we do GPU-GPU coupling they will have upgraded already (@simone-silvestri do you plan to change compat to GPUArrays v11?). And it's better to go to the new version anyway. Green light from my side!

[simone-silvestri]

There has been a feature removal in [email protected] that breaks a bunch of code for GPU oceananigans see this PR. So for the moment until the issue has been resolved, we have pinned a previous version of GPU arrays. Hopefully, if it is solved soon, we can move to the new version.

[maximilian-gelbrecht]

We are in no hurry with this. I think we can wait until Oceananigans is compatible as well.

[milankl]

Because even if we run CPU-GPU with Oceananigans this will create a compat conflict? Yes makes sense

[milankl]

@simone-silvestri I'd love to update to GPUArrays v11, but I believe that would currently cause a conflict with Oceananigans?

[giordano]

but I believe that would currently cause a conflict with Oceananigans?

CliMA/Oceananigans.jl#4081