70aefe3449
The current handling for SPIR-V memory semantics is very specific to the wording in the SPIR-V spec, which breaks its handling of OpenCL (compared to what we had working downstream before merging upstream). Update/relax the logic here to support CL's barrier(CLK_GLOBAL_MEM_FENCE); Reviewed-by: Jason Ekstrand <jason@jlekstrand.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10165>