search for: mem_fenc

...barrier/fence intrinsics, we have considered using customized alias analysis passes. However, we would like to move away from using customized passes and would like to use standard llvm mechanisms as much as possible. What do people think about adding an llvm intrinsic, something like llvm.opencl.mem_fence(i32) (or named something that doesn't have opencl in the name, llvm.addrspace_fence?), which acts as a fence for a single given address space (assuming again that there's no problem with implementing these things as a series of different functions to get the full effect), and which prevent...

...fence intrinsics, we have considered using customized alias analysis passes. However, we would like to move away from using customized passes and would like to use standard llvm mechanisms as much as possible. > > What do people think about adding an llvm intrinsic, something like llvm.opencl.mem_fence(i32) (or named something that doesn't have opencl in the name, llvm.addrspace_fence?), which acts as a fence for a single given address space (assuming again that there's no problem with implementing these things as a series of different functions to get the full effect), and which prevent...

...trinsics, we have considered using customized alias analysis passes. However, we would like to move away from using customized passes and would like to use standard llvm mechanisms as much as possible. >> >> What do people think about adding an llvm intrinsic, something like llvm.opencl.mem_fence(i32) (or named something that doesn't have opencl in the name, llvm.addrspace_fence?), which acts as a fence for a single given address space (assuming again that there's no problem with implementing these things as a series of different functions to get the full effect), and which prevent...

...we have considered using customized alias analysis passes. However, we would like to move away from using customized passes and would like to use standard llvm mechanisms as much as possible. >>> >>> What do people think about adding an llvm intrinsic, something like llvm.opencl.mem_fence(i32) (or named something that doesn't have opencl in the name, llvm.addrspace_fence?), which acts as a fence for a single given address space (assuming again that there's no problem with implementing these things as a series of different functions to get the full effect), and which prevent...

On Dec 26, 2013, at 10:38 PM, Andrew Trick <atrick at apple.com> wrote: >> >> >> I think "memfence" could be an issue if we use the attribute to summarize LLVM atomic load/store and fence instructions (in addition to OpenCL barriers). >> >> I have no idea what semantics you would attach to it in this case. I've not seen any clear explanation of

...have considered using > customized alias analysis passes. However, we would like to move away from > using customized passes and would like to use standard llvm mechanisms as > much as possible. > > What do people think about adding an llvm intrinsic, something like > llvm.opencl.mem_fence(i32) (or named something that doesn't have opencl in > the name, llvm.addrspace_fence?), which acts as a fence for a single given > address space (assuming again that there's no problem with implementing > these things as a series of different functions to get the full effect), an...

...t;> customized alias analysis passes. However, we would like to move away from >> using customized passes and would like to use standard llvm mechanisms as >> much as possible. >> >> What do people think about adding an llvm intrinsic, something like >> llvm.opencl.mem_fence(i32) (or named something that doesn't have opencl in >> the name, llvm.addrspace_fence?), which acts as a fence for a single given >> address space (assuming again that there's no problem with implementing >> these things as a series of different functions to get the full...