[MLIR][GPUToLLVMSPV] Use global & local memory scope for GPUBarrierConversion (#169026) The MLIR [GPU dialect docs](https://mlir.llvm.org/docs/Dialects/GPU/#gpubarrier-gpubarrierop) specify that gpu::BarrierOp should make *all memory accesses* visible to all work items in the workgroup. Current implementation uses only CLK_LOCAL_MEM_FENCE, which per the [OpenCL specification](https://registry.khronos.org/OpenCL/sdk/3.0/docs/man/html/barrier.html) guarantees visibility of only *local memory accesses*. This PR changes the barrier conversion to use CLK_LOCAL_MEM_FENCE | CLK_GLOBAL_MEM_FENCE, ensuring both local and global memory operations are properly synchronized per the MLIR spec. This issue was discovered while investigating numerical instabilities on Intel Battlemage, where race conditions occurred due to incomplete memory synchronization.
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.