OpenCL kernel binary cache invalidation strategy across driver updates
Context Applications that cache OpenCL kernel binaries via clGetProgramInfo(CL_PROGRAM_BINARIES) and reload them with clCreateProgramWithBinary face a gap: the specification guarantees binary compatibility only for the exact same CL_DEVICE_NAME and CL_DRIVER_VERSION pair, yet provides no mechanism to detect when a cached binary has become stale. Constraints