Open stellaraccident opened 1 year ago
Tombstone hmmmm, P2..?
No, pretty sure it is broken -- just left this here to pick up.
Which version of MSVC? (pretty sure we are hitting at least one other one there https://github.com/google/jax/issues/16394 but that's with bazel too, so may be completely different)
Leaving here as a tombstone. I have disabled the compiler api_test.py on Windows and need to fix it.
Something in here is causing a word to be corrupted, which always seems to be the high (memory order) word of the MlirContext.ptr. It makes no sense. I can step through in the debugger, and all looks fine until stepping into an inlined
getContext()
function (can be triggered through multiple paths). Then the value flips with the low order 32bits of the pointer being corrupted. Nothing else is going on and significant bisecting has been done to see that it is a problem at this point. I suspect a compiler bug.Also, during the investigation, it was noted that this method is leaking MLIRContext references:
The py::cast needs a return value policy to take ownership.