Matti Picus <matti(a)picus.org.il> writes:
It seems the way to proceed would be by creating another parallel
low-level interface to the system calls via cffi without pyboost, and
then slowly replace the existing low-level interfaces with the new ones
until we can eventually remove the old ones. Hopefully that will not
cause too many memory leaks in the transition.
Since many of the objects interact, we'd also have to build an interface
layer between the boost-python wrappers and the cffi ones--which I'd
IOW, I'm not sure it makes sense to have both in the same tree. I'd say
let's start slow by just wrapping the bare necessities from Context,
CommandQueue, Buffer, Program, and Kernel. (while taking notes on what
was left out) That should give us a proof-of-concept idea of how
difficult (and successful) this is all going to be.
How is the coverage of the test suite, can we be reasonably confident
that if tests pass and the benchmark does not suffer, the package still
Coverage is good. If it passes, it's in releasable state.