search for: addrspace_f

...es. 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 prevents even noalias pointers from being moved across it? Alternatively (possibly nicer) w...

...er, 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 prevents even noalias pointers from being moved across it? > > Alternatively (possibly...

...ould 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 prevents even noalias pointers from being moved across it? >> >> Alternatively (...

...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 prevents even noalias pointers from being moved across it? >>> >>> Altern...

...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 prevents even noalias pointers from being moved across it? > > Alternat...

...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 prevents even noalias pointers from being moved across it? >&g...