aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Frontend/InitPreprocessor.cpp
diff options
context:
space:
mode:
authorAbhinav Gaba <abhinav.gaba@intel.com>2025-08-15 11:49:35 -0700
committerGitHub <noreply@github.com>2025-08-15 11:49:35 -0700
commit79cf877627ec341c62f64e25a44f3ba340edad1e (patch)
treea29e2abb33f9b2b6ee2dc52643aba8a76b42ec1a /clang/lib/Frontend/InitPreprocessor.cpp
parent82caa251d4e145b54ea76236213617076f254c2b (diff)
downloadllvm-79cf877627ec341c62f64e25a44f3ba340edad1e.zip
llvm-79cf877627ec341c62f64e25a44f3ba340edad1e.tar.gz
llvm-79cf877627ec341c62f64e25a44f3ba340edad1e.tar.bz2
[Offload] Introduce dataFence plugin interface. (#153793)
The purpose of this fence is to ensure that any `dataSubmit`s inserted into a queue before a `dataFence` finish before finish before any `dataSubmit`s inserted after it begin. This is a no-op for most queues, since they are in-order, and by design any operations inserted into them occur in order. But the interface is supposed to be functional for out-of-order queues. The addition of the interface means that any operations that rely on such ordering (like ATTACH map-type support in #149036) can invoke it, without worrying about whether the underlying queue is in-order or out-of-order. Once a plugin supports out-of-order queues, the plugin can implement this function, without requiring any change at the libomptarget level. --------- Co-authored-by: Alex Duran <alejandro.duran@intel.com>
Diffstat (limited to 'clang/lib/Frontend/InitPreprocessor.cpp')
0 files changed, 0 insertions, 0 deletions