I ran into a bug caused by overriding the implementation of an operator only in the TF runtime, not in the TF linked to the compiler. The runtime implementation was doing different calls to AllocatePersistentBuffer than what the compiler expected. This caused weird data corruption issues.
This PR implements a way to prevent such issues in the future.
I ran into a bug caused by overriding the implementation of an operator only in the TF runtime, not in the TF linked to the compiler. The runtime implementation was doing different calls to AllocatePersistentBuffer than what the compiler expected. This caused weird data corruption issues.
This PR implements a way to prevent such issues in the future.