Andreas Klöckner

This also came up recently in https://github.com/inducer/pycuda/issues/305#issuecomment-887761332. PyCUDA currently assumes that each context can only be active in a single thread. It appears that this was true up until CUDA...

How come this got closed? The question you raised is a real concern to my mind, and I wouldn't be opposed to the issue staying open.

PyCUDA isn't doing anything special with memcpy. It just calls the corresponding CUDA function. For an additional speedboost, you can use "page-locked" memory (on the host side).

Yep, agree the the name should be decided once and then not messed with.

Thanks for reporting this! #483 fixes the unassigned variable (which is definitely a bug). ed5d1458abb07f7d30de4854b1e4f427480e52df was an attempt to make type inference succeed, but given that `insn1` is self-referential, I...

That seems similar to ed5d1458abb07f7d30de4854b1e4f427480e52df in its approach, however I'm not sure either approach necessarily yields a consistent treatment of self-referential assignments. Just skipping them basically ignores type constraints that...

Thanks for the report! My read on this is that the (quite old, quite long in the tooth version of Boost.Python that ships with PyCUDA is incompatible with Python 3.11....

I saw you filed https://github.com/boostorg/python/issues/388. If you're sure you disabled the shipped boost and the updated Boost.Python was used instead, then it may just be that Boost.Python itself still needs...

We could try simply applying this patch if that works: https://github.com/boostorg/python/commit/a218babc8daee904a83f550fb66e5cb3f1cb3013.

No, that means I'm hoping you can apply that patch to the source under `bpl-subset` and report back.