saiislam marked an inline comment as done.
saiislam added inline comments.
================
Comment at: clang/test/CodeGenCXX/builtin-amdgcn-fence-failure.cpp:5
+
+void test_amdgcn_fence_failure() {
+
----------------
b-sumner wrote:
> JonChesterfield wrote:
> > arsenm wrote:
> > > Does this really depend on C++? Can it use OpenCL like the other builtin
> > > tests?This also belongs in a Sema* test directory since it's checking an
> > > error
> > Making it opencl-only would force some of the openmp runtime to be written
> > in opencl, which is not presently the case. Currently that library is
> > written in a dialect of hip, but there's a plan to implement it in openmp
> > instead.
> >
> > I'd much rather this builtin work from any language, instead of tying it to
> > opencl, as that means one can use it from openmp target regions.
> I thought the question was about this test itself. The test being in
> CodeGenOpenCL doesn't affect whether other languages can use the builtin.
> Why not put this test in CodeGenOpenCL alongside all of the other
> builtins-amdgcn-*.cl ?
This test is basically relying on implementation of sync scope in the AMDGCN
backend to check for validity, and is not testing the code generation
capability. Doesn't it make more sense in Sema directory?
Won't putting it in SemaOpenCL or SemaOpenCLCXX indicate some kind of relation
with OpenCL?
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D75917/new/
https://reviews.llvm.org/D75917
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
