Graham Markall

It looks like Numba doesn't handle it very gracefully when `CUDA_HOME` is incorrectly set (see traceback in report for #9216). We can improve on the feedback to the user: *...

CUDA: support array copy similar to `np.copy`

1

Creating a copy of a device array is not trivial, and should be. A couple of current workarounds are: ```python # Variant 1 @numba.vectorize(['float32(float32)'], target='cuda') def copy(x): return x #...

CUDA: allow the user to specify that a kernel will have low occupancy in the `@cuda.jit` decorator

1

Some kernels will need to be called with low occupancy in the context of a workflow, and there isn't always a sensible way to avoid this. It would be nice...

`raise` and `assert` do not work correctly in CUDA device functions

1

The following: ```python from numba import cuda @cuda.jit(device=True) def f(): raise ValueError('Error') @cuda.jit(debug=True, opt=False) def kernel(): f() kernel[1, 1]() ``` results in an error like: ``` Traceback (most recent call...

Move Azure to use macos-13

2

macos-12 is deprecated and will be removed soon.

Merge of `main` into #986 - I am not permitted to push to that branch, so testing here.