en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/openmp/libomptarget/test/mapping/target_update_array_extension.c#24f836e8 [OpenMP][libomptarget] Separate lit tests for different offloading targets (2/2)This patch fuses the RUN lines for most libomptarget tests. The previous patchD101315 created separate test targets for each supported offloading triple.This patch updates the RUN lines in libomptarget tests to use a generic runline independent of the offloading target selected for the lit instance.In cases, where no RUN line was defined for a specific offloading target,the corresponding target is declared as XFAIL. If it turns out that a testactually supports the target, the XFAIL line can be removed.Differential Revision: https://reviews.llvm.org/D101326 List of files: /llvm-project-15.0.7/openmp/libomptarget/test/mapping/target_update_array_extension.c Tue, 27 Apr 2021 13:50:53 +0000 Joachim Protze <protze@itc.rwth-aachen.de> http://172.16.0.5:8080/history/llvm-project-15.0.7/openmp/libomptarget/test/mapping/target_update_array_extension.c#5ab43989 [OpenMP] Fix `omp target update` for array extensionOpenMP TR8 sec. 2.15.6 "target update Construct", p. 183, L3-4 states:> If the corresponding list item is not present in the device data> environment and there is no present modifier in the clause, then no> assignment occurs to or from the original list item.L10-11 states:> If a present modifier appears in the clause and the corresponding> list item is not present in the device data environment then an> error occurs and the program termintates.(OpenMP 5.0 also has the first passage but without mention of thepresent modifier of course.)In both passages, I assume "is not present" includes the case ofpartially but not entirely present. However, without this patch, thetarget update directive misbehaves in this case both with and withoutthe present modifier. For example:``` #pragma omp target enter data map(to:arr[0:3]) #pragma omp target update to(arr[0:5]) // might fail on data transfer #pragma omp target update to(present:arr[0:5]) // might fail on data transfer```The problem is that `DeviceTy::getTgtPtrBegin` does not return a nullpointer in that case, so `target_data_update` sees the data as fullypresent, and the data transfer then might fail depending on the targetdevice. However, without the present modifier, there should never bea failure. Moreover, with the present modifier, there should alwaysbe a failure, and the diagnostic should mention the present modifier.This patch fixes `DeviceTy::getTgtPtrBegin` to return null when`target_data_update` is the caller. I'm wondering if it should do thesame for more callers.Reviewed By: grokos, jdoerfertDifferential Revision: https://reviews.llvm.org/D85246 List of files: /llvm-project-15.0.7/openmp/libomptarget/test/mapping/target_update_array_extension.c Wed, 05 Aug 2020 13:00:12 +0000 Joel E. Denny <jdenny.ornl@gmail.com>