Concerning an issue with the current wait_for_fences implementation for the ANY case, where a pending fence completion call might infer with following function calls, signalling the wrong event:
store an event along each fence, will be set once the fence gets signalled? We can safely reset the event on ResetFences due to externally synchronization requirement
Concerning an issue with the current wait_for_fences implementation for the ANY case, where a pending fence completion call might infer with following function calls, signalling the wrong event: