Graham Markall
Graham Markall
I've added "discussion" as this seems most appropriate (and I don't want to leave this unlabelled because then it looks like the label was forgotten).
On possibility is for the return value to be on the caller's stack and passed as a pointer. Since we already pass the return pointer to device functions (because the...
@chenzhekl It doesn't appear to have been removed - can you open a new issue describing what you're observing if you're having a problem please? Also, note that the most...
Thanks, I can reproduce the issue. Reproducer that runs the same function in the jitted and non-jitted variants: ```python import numpy as np from numba import njit def histogram(): return...
I'm going to guess this might be tractable for someone who's started to get familiar with Numba's internals, perhaps with some guidance / mentoring, so I'll label this as a...
(cc @PhilipVinc, c.f. https://numba.discourse.group/t/hashing-an-array/861)
> For info: If I tackle this issue with a PR how long will it take for it to end up in a released branch? That's hard to answer because...
/azp run
@yashssh Will numba/numba#9676 also be needed in Numba for it to work with LLVM >= 17? Would @detrout need to grab that and incorporate it into the Debian sources?
With this PR and the package built by #1226, I get: ``` $ gdb --args python runtests.py (gdb) run Starting program: /home/gmarkall/miniforge3/envs/test-llvmlite-20-py311/bin/python runtests.py ..s.. Program received signal SIGSEGV, Segmentation fault....