Tidy up of tests

- remove a lot of whitespace
- add end of file lines
- remove no longer required comments or messages

Author: agozillon

test/fortran-map-tests/SWDEV-564425-simple.f90

@@ -63,6 +63,3 @@ program udt_release
 
   print*, "======= FORTRAN Test Passed! ======="
 end program
-
-! $BUILD_DIR/bin/flang -fopenmp-version=60 -I$FORTRAN_OMP_MOD_FILES --offload-arch=gfx90a -fopenmp SWDEV-564425-simple.f90 -o SWDEV-564425-simple.out
-! /COD/2025-10-25/aomp/llvm/bin/flang -I$FORTRAN_OMP_MOD_FILES --offload-arch=gfx90a -fopenmp SWDEV-564425.f90 -o SWDEV-564425.out

test/fortran-map-tests/SWDEV-564425-v2-alloca-parent-and-children.f90

@@ -40,11 +40,6 @@ program udt_release
   allocate(obj%dtype_nest%dtype_nest%arr3(n))
   allocate(obj%dtype_nest%dtype_nest%scalar_ptr)
 
-! Present checking and sending separately as if we send it in a single map/present check it in a single map
-! we end up allocating bits and pieces implicitly due to the implicit binding parent map, but this seems
-! analogous to Clang behaviour. It may need a bit of a rethink though, or a verification if it's the correct
-! OpenMP behaviour.
-
 !$omp target enter data map(ref_ptr, to: obj%arr, obj%dtype_nest2%arr3, obj%dtype_nest2%scalar_ptr, obj%dtype_nest%scalar_ptr, obj%dtype_nest%dtype_nest%arr3, obj%dtype_nest%dtype_nest%scalar_ptr)
 !$omp target enter data map(ref_ptr, present, storage: obj%arr, obj%dtype_nest2%arr3, obj%dtype_nest2%scalar_ptr, obj%dtype_nest%scalar_ptr, obj%dtype_nest%dtype_nest%arr3, obj%dtype_nest%dtype_nest%scalar_ptr)
 
@@ -103,9 +98,6 @@ program udt_release
    stop 1
 endif
 
-! NOTE: We currently need to map the derived type descriptor + data when mapping this type of 
-! construct, we might be able to tweak things to skip this part of the mapping in the future.
-! But for simplicities sake I've left it as-is for the first iteration.
 if(omp_target_is_present(C_LOC(obj), omp_get_default_device()) == 0) then
    print *, "After enter: obj parent structure NOT on device"
 else
@@ -175,9 +167,6 @@ program udt_release
 
 !$omp target update from(obj%arr, obj%dtype_nest2%arr3, obj%dtype_nest2%scalar_ptr, obj%dtype_nest%scalar_ptr, obj%dtype_nest%dtype_nest%arr3, obj%dtype_nest%dtype_nest%scalar_ptr)
 
-! ! to make sure this can be used and ref counts correctly we might have to opt out of mapping the intermediate bits for exit/enter
-! ! ! !!$omp target exit data map(ref_ptee, from: obj%arr, obj%dtype_nest2%arr3, obj%dtype_nest2%scalar_ptr, obj%dtype_nest%scalar_ptr, obj%dtype_nest%dtype_nest%arr3, obj%dtype_nest%dtype_nest%scalar_ptr)
-
    print *, obj%arr
    print *, obj%dtype_nest2%arr3
    print *, obj%dtype_nest%dtype_nest%arr3

test/fortran-map-tests/SWDEV-564425-v2-alloca-parent.f90

@@ -37,11 +37,6 @@ program udt_release
   allocate(obj%dtype_nest%dtype_nest%arr3(n))
   allocate(obj%dtype_nest%dtype_nest%scalar_ptr)
 
-! Present checking and sending separately as if we send it in a single map/present check it in a single map
-! we end up allocating bits and pieces implicitly due to the implicit binding parent map, but this seems
-! analogous to Clang behaviour. It may need a bit of a rethink though, or a verification if it's the correct
-! OpenMP behaviour.
-
 !$omp target enter data map(ref_ptr, to: obj%arr, obj%dtype_nest2%arr3, obj%dtype_nest2%scalar_ptr, obj%dtype_nest%scalar_ptr, obj%dtype_nest%dtype_nest%arr3, obj%dtype_nest%dtype_nest%scalar_ptr)
 !$omp target enter data map(ref_ptr, present, storage: obj%arr, obj%dtype_nest2%arr3, obj%dtype_nest2%scalar_ptr, obj%dtype_nest%scalar_ptr, obj%dtype_nest%dtype_nest%arr3, obj%dtype_nest%dtype_nest%scalar_ptr)
 
@@ -52,7 +47,6 @@ program udt_release
 print *, "obj%dtype_nest%dtype_nest%arr3 ref_ptr on device"
 print *, "obj%dtype_nest%dtype_nest%scalar_ptr ref_ptr on device"
 
-
 if(omp_target_is_present(C_LOC(obj%arr), omp_get_default_device()) == 0) then
    print *, "After enter: obj%arr ref_ptee NOT on device"
 else

test/fortran-map-tests/SWDEV-564425-v2.f90

@@ -36,11 +36,6 @@ program udt_release
   allocate(obj%dtype_nest%dtype_nest%arr3(n))
   allocate(obj%dtype_nest%dtype_nest%scalar_ptr)
 
-! Present checking and sending separately as if we send it in a single map/present check it in a single map
-! we end up allocating bits and pieces implicitly due to the implicit binding parent map, but this seems
-! analogous to Clang behaviour. It may need a bit of a rethink though, or a verification if it's the correct
-! OpenMP behaviour.
-
 !$omp target enter data map(ref_ptr, to: obj%arr, obj%dtype_nest2%arr3, obj%dtype_nest2%scalar_ptr, obj%dtype_nest%scalar_ptr, obj%dtype_nest%dtype_nest%arr3, obj%dtype_nest%dtype_nest%scalar_ptr)
 !$omp target enter data map(ref_ptr, present, storage: obj%arr, obj%dtype_nest2%arr3, obj%dtype_nest2%scalar_ptr, obj%dtype_nest%scalar_ptr, obj%dtype_nest%dtype_nest%arr3, obj%dtype_nest%dtype_nest%scalar_ptr)
 
@@ -51,7 +46,6 @@ program udt_release
 print *, "obj%dtype_nest%dtype_nest%arr3 ref_ptr on device"
 print *, "obj%dtype_nest%dtype_nest%scalar_ptr ref_ptr on device"
 
-
 if(omp_target_is_present(C_LOC(obj%arr), omp_get_default_device()) == 0) then
    print *, "After enter: obj%arr ref_ptee NOT on device"
 else

test/fortran-map-tests/SWDEV-564425-v3-alloca-parent-and-children.f90

@@ -40,11 +40,6 @@ program udt_release
   allocate(obj%dtype_nest%dtype_nest%arr3(n))
   allocate(obj%dtype_nest%dtype_nest%scalar_ptr)
 
-! Present checking and sending separately as if we send it in a single map/present check it in a single map
-! we end up allocating bits and pieces implicitly due to the implicit binding parent map, but this seems
-! analogous to Clang behaviour. It may need a bit of a rethink though, or a verification if it's the correct
-! OpenMP behaviour.
-
 !$omp target enter data map(ref_ptee, to: obj%arr, obj%dtype_nest2%arr3, obj%dtype_nest2%scalar_ptr, obj%dtype_nest%scalar_ptr, obj%dtype_nest%dtype_nest%arr3, obj%dtype_nest%dtype_nest%scalar_ptr)
 
 if(omp_target_is_present(C_LOC(obj%arr), omp_get_default_device()) == 0) then

test/fortran-map-tests/SWDEV-564425-v3-alloca-parent.f90

@@ -37,11 +37,6 @@ program udt_release
   allocate(obj%dtype_nest%dtype_nest%arr3(n))
   allocate(obj%dtype_nest%dtype_nest%scalar_ptr)
 
-! Present checking and sending separately as if we send it in a single map/present check it in a single map
-! we end up allocating bits and pieces implicitly due to the implicit binding parent map, but this seems
-! analogous to Clang behaviour. It may need a bit of a rethink though, or a verification if it's the correct
-! OpenMP behaviour.
-
 !$omp target enter data map(ref_ptee, to: obj%arr, obj%dtype_nest2%arr3, obj%dtype_nest2%scalar_ptr, obj%dtype_nest%scalar_ptr, obj%dtype_nest%dtype_nest%arr3, obj%dtype_nest%dtype_nest%scalar_ptr)
 
 if(omp_target_is_present(C_LOC(obj%arr), omp_get_default_device()) == 0) then

test/fortran-map-tests/SWDEV-564425-v3.f90

@@ -36,11 +36,6 @@ program udt_release
   allocate(obj%dtype_nest%dtype_nest%arr3(n))
   allocate(obj%dtype_nest%dtype_nest%scalar_ptr)
 
-! Present checking and sending separately as if we send it in a single map/present check it in a single map
-! we end up allocating bits and pieces implicitly due to the implicit binding parent map, but this seems
-! analogous to Clang behaviour. It may need a bit of a rethink though, or a verification if it's the correct
-! OpenMP behaviour.
-
 !$omp target enter data map(ref_ptee, to: obj%arr, obj%dtype_nest2%arr3, obj%dtype_nest2%scalar_ptr, obj%dtype_nest%scalar_ptr, obj%dtype_nest%dtype_nest%arr3, obj%dtype_nest%dtype_nest%scalar_ptr)
 
 if(omp_target_is_present(C_LOC(obj%arr), omp_get_default_device()) == 0) then

test/fortran-map-tests/SWDEV-564425-v4-alloca-parent-and-children.f90

@@ -40,11 +40,6 @@ program udt_release
   allocate(obj%dtype_nest%dtype_nest%arr3(n))
   allocate(obj%dtype_nest%dtype_nest%scalar_ptr)
 
-! Present checking and sending separately as if we send it in a single map/present check it in a single map
-! we end up allocating bits and pieces implicitly due to the implicit binding parent map, but this seems
-! analogous to Clang behaviour. It may need a bit of a rethink though, or a verification if it's the correct
-! OpenMP behaviour.
-
 !$omp target enter data map(ref_ptee, to: obj%arr)
 !$omp target enter data map(ref_ptee, to: obj%dtype_nest2%arr3)
 !$omp target enter data map(ref_ptee, to: obj%dtype_nest2%scalar_ptr)

test/fortran-map-tests/SWDEV-564425-v4-alloca-parent.f90

@@ -38,17 +38,6 @@ program udt_release
   allocate(obj%dtype_nest%dtype_nest%arr3(n))
   allocate(obj%dtype_nest%dtype_nest%scalar_ptr)
 
-
-! Present checking and sending separately as if we send it in a single map/present check it in a single map
-! we end up allocating bits and pieces implicitly due to the implicit binding parent map, but this seems
-! analogous to Clang behaviour. It may need a bit of a rethink though, or a verification if it's the correct
-! OpenMP behaviour.
-
-! it's somewhat illegal to have the obj in the follow up ref_ptee as we've already mapped chunks of
-! it before when mapping members in the ref_ptr enter map, it will currently work but it shouldn't be
-! encouraged as there's no guarantee it'll remain that way or be portable. And as we're mapping members
-! of obj (the descriptors of the pointer/allocatable members) we actually have to map the contiguous blocks
-! of data.
 !$omp target enter data map(ref_ptr, to: obj, obj%arr, obj%dtype_nest2%arr3, obj%dtype_nest2%scalar_ptr, obj%dtype_nest%scalar_ptr, obj%dtype_nest%dtype_nest%arr3, obj%dtype_nest%dtype_nest%scalar_ptr)
 !$omp target enter data map(ref_ptr, present, storage: obj, obj%arr, obj%dtype_nest2%arr3, obj%dtype_nest2%scalar_ptr, obj%dtype_nest%scalar_ptr, obj%dtype_nest%dtype_nest%arr3, obj%dtype_nest%dtype_nest%scalar_ptr)
 
@@ -107,8 +96,6 @@ program udt_release
    stop 1
 endif
 
-! We technically map bits of the object when we specify the mapping of the
-! descriptors for each of the member maps.
 if(omp_target_is_present(C_LOC(obj), omp_get_default_device()) == 0) then
    print *, "After enter: obj parent structure NOT on device"
    print*, "======= FORTRAN Test Failed! ======="

test/fortran-map-tests/SWDEV-564425-v5-alloca-parent-and-children.f90

@@ -40,11 +40,6 @@ program udt_release
   allocate(obj%dtype_nest%dtype_nest%arr3(n))
   allocate(obj%dtype_nest%dtype_nest%scalar_ptr)
 
-! Present checking and sending separately as if we send it in a single map/present check it in a single map
-! we end up allocating bits and pieces implicitly due to the implicit binding parent map, but this seems
-! analogous to Clang behaviour. It may need a bit of a rethink though, or a verification if it's the correct
-! OpenMP behaviour.
-
 !$omp target enter data map(ref_ptr, to: obj%arr)
 !$omp target enter data map(ref_ptr, present, storage: obj%arr)