Freddie Witherden <[email protected]> writes: > I did consider improving it however my attempts to contact the > developer resulted in an e-mail bounce.
He was around at least until June. Lev, you here? >> Second, as an answer to your question: pycuda.autoinit is by no >> means a required part of PyCUDA. Just do your own initialization >> (and also initialize PyCUDA), and tell your users to call your init >> instead of PyCUDA's. > > It is, however, necessary to pop() the context before program > termination, no? As this is, to an extent, my issue. Currently one > option, potentially, is to create a wrapper class which takes care of > calling self._ctx.pop() in __del__ and takes care of creating the > context on __init__. I can then retain an handle to this in my CUBLAS > class so ensure that it will be kept around. (Although am yet to work > out the details so my idea is possibly flawed). IIUC, the issue is ordering of CUBLAS context destruction vs PyCUDA context pop, right? If you're in charge of doing both, then you've got control of the order. What am I missing? Andreas _______________________________________________ PyCUDA mailing list [email protected] http://lists.tiker.net/listinfo/pycuda
