# CUDA.jl 2.0: Per-thread streams, Float16, CUSPARSE clean-up

**URL:** <https://discourse.julialang.org/t/cuda-jl-2-0-per-thread-streams-float16-cusparse-clean-up/47630>\
**Category:** Package Announcements\
**Created:** [October 2, 2020, 7:45am UTC](https://discourse.julialang.org/t/cuda-jl-2-0-per-thread-streams-float16-cusparse-clean-up/47630 "2020-10-02T07:45:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![maleadt](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/maleadt/32/10097_2.png) [@maleadt](https://discourse.julialang.org/u/maleadt)\
**Post date:** [October 2, 2020, 7:45am UTC](https://discourse.julialang.org/t/cuda-jl-2-0-per-thread-streams-float16-cusparse-clean-up/47630/1 "2020-10-02T07:45:07Z")

</div>

Hi all,

I’ve just tagged and release CUDA.jl 2.0, with several new features: [https://juliagpu.org/2020-10-02-cuda\_2.0/](https://juliagpu.org/2020-10-02-cuda_2.0/)

This release is slightly breaking because of the following changes:

- per-thread streams: unlikely to break anything since few people are using threads with CUDA.jl
- CUSPARSE clean-up: for example, `switch2XXX` methods are now `convert` methods
- array dispatch changes: view/reinterpret/reshape are now represented using Base’s wrappers.

This last point isn’t technically breaking, but it’s likely that some methods that still dispatch on `::CuArray` won’t get considered anymore now that, e.g., `view(...) = ::SubArray{<:CuArray}`. As a result, fall-back Base methods might get used instead of CUDA-specific implementations, triggering scalar iteration or invalid pointer conversions (GPU array to CPU pointer). The fix is to use `DenseCuArray` (if your method needs a `CuPtr`), `StridedCuArray` (for a `CuPtr` + strides) or `AnyCuArray` (for anything that can be used in a kernel). Please file issues if you encounter this with array operations from CUDA.jl or GPUArrays.jl.

Finally, since this is a breaking release, dependent packages like Flux.jl still needs to be updated or bumped so many users won’t be able to install CUDA.jl 2.0 just yet.

---

<div class="post-metadata">

**Author:** ![Palli](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/palli/32/3380_2.png) [@Palli](https://discourse.julialang.org/u/Palli)\
**Post date:** [October 2, 2020, 4:11pm UTC](https://discourse.julialang.org/t/cuda-jl-2-0-per-thread-streams-float16-cusparse-clean-up/47630/2 "2020-10-02T16:11:15Z")

</div>

> initial support for Float16 [here assuming Julia’s type] CUBLAS wrappers can be used with (B)Float16 inputs […]
> 
> ```julia
> julia> using BFloat16s
> 
> ```
> 
> […] Alternatively, CUBLAS can be configured to automatically down-cast 32-bit inputs to Float16.

How does this compare to CUDA from other languages, C++, or indirectly from Python?

My understanding is that Nvidia has this new type, and makes life easy for C++ programmers, that otherwise would have needed to replace lots of types.

Since you can downcast from Float32, I assume also from Float64 (just not directly, maybe not a big worry as nobody uses anyway… for ANNs)?

Python libraries, e.g. PyTorch has had some advantage over Julia and pure Julia packages, is this likely to close the gap (when Flux etc. support this updated wrapper). [You can also use PyTorch.jl/**[ThArrays.jl](https://github.com/TuringLang/ThArrays.jl)** and bypass this wrapper. Is that something you would mix and match with the wrapper?]

---

<div class="post-metadata">

**Author:** ![maleadt](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/maleadt/32/10097_2.png) [@maleadt](https://discourse.julialang.org/u/maleadt)\
**Post date:** [October 2, 2020, 4:46pm UTC](https://discourse.julialang.org/t/cuda-jl-2-0-per-thread-streams-float16-cusparse-clean-up/47630/3 "2020-10-02T16:46:16Z")

</div>

> [@Palli](#):
>
> My understanding is that Nvidia has this new type, and makes life easy for C++ programmers, that otherwise would have needed to replace lots of types.

That’s the global mode mentioned on the blogpost that lets CUBLAS downcast, there’s not really a special type, at least not for the user. Automatic downcast from Float64 isn’t currently supported by CUBLAS now though.