This is more of a heads up, because it’s presumably coming in the LLVM 16 timeframe, but this was reported internally by the llvm developers. Because we live at LLVM head, I’ll be forced to deal with this before llvmlite/numba, so I’ll report back as I get a better picture.
2 Likes
Thanks for the heads-up! Are you running into mandatory use of opaque pointers yet?
Thankfully no. I just did a quick grep and it looks like numba doesn’t call Value.element_type() so maybe that will end up being a non-issue.