call void @dx.op.rawBufferStore.f64 has been revealed to potentially have different implementations depending on whether the resource is created as reserved or committed. This reveals the fact that the effort to move all resources to reserved means that the offload test suite will lose coverage on implementations for intrinsics on committed resources.
There should be a way in the offload test suite to specify whether to use reserved or committed resources, and ideally, lit should expose this option so that certain tests can XFAIL on reserved resource implementation, while succeeding on committed resource implementations.
By default, all tests should be run on both reserved and committed resources. And perhaps there should be a lit target added to specify whether to run test directories using reserved or committed resources.