Merge pull request #70 from zbeekman/fix-whitespace-1.x

Fix sloppy EOL & EOF whitespace on 1.x branch

Author: zbeekman

CAF_ABI.md

@@ -1,5 +1,5 @@
-[This document is formatted with GitHub-Flavored Markdown.              ]:# 
-[For better viewing, including hyperlinks, read it online at            ]:# 
+[This document is formatted with GitHub-Flavored Markdown.              ]:#
+[For better viewing, including hyperlinks, read it online at            ]:#
 [https://github.com/sourceryinstitute/opencoarrays/blob/master/CAF_API.md]:#
 
 # OpenCoarrays Application Binary Interface (ABI) #
@@ -9,13 +9,13 @@
 * [Definitions and types]
 * [Provided functions]
 
-This document describes the OpenCoarrays application binary interface (ABI) through 
-which a compiler accesses coarray functionality.  As such, the target audience for 
+This document describes the OpenCoarrays application binary interface (ABI) through
+which a compiler accesses coarray functionality.  As such, the target audience for
 this document is compiler developers.  Most application developers need only write
 standard-conforming Fortran 2008 or 2015 and compile their code with the OpenCoarrays
-'caf' compiler wrapper without knowledge of the ABI.  
+'caf' compiler wrapper without knowledge of the ABI.
 
-The actual function names in this document have a PREFIX in the source code to avoid 
+The actual function names in this document have a PREFIX in the source code to avoid
 name clashes.  The prefix can be vendor-specific.
 
 ## <a name="to-do">To Do</a> ##

CMakeLists.txt

@@ -28,14 +28,14 @@ if ("${CMAKE_Fortran_COMPILER_ID}" MATCHES "GNU" )
   set(gfortran_compiler true)
 # add_definitions(-DPREFIX_NAME=_gfortran_caf_)
 else()
-  message(WARNING 
+  message(WARNING
     "\n"
     "Attempting to build with untested Fortran compiler: ${CMAKE_Fortran_COMPILER_ID}. "
     "Please report any failures to [email protected]\n\n"
   )
 endif()
 
-if (NOT CMAKE_VERSION VERSION_LESS 3.3.1) 
+if (CMAKE_VERSION VERSION_GREATER 3.2.3)
   # Detect Fortran compiler version directly
   if(gfortran_compiler AND (CMAKE_Fortran_COMPILER_VERSION VERSION_GREATER 5.0.0))
     set(opencoarrays_aware_compiler true)
@@ -70,7 +70,7 @@ include_directories(${CMAKE_CURRENT_SOURCE_DIR}/src)
 add_subdirectory(src)
 add_subdirectory(install_prerequisites)
 
-install(EXPORT OpenCoarraysTargets 
+install(EXPORT OpenCoarraysTargets
   NAMESPACE
     OpenCoarrays::
   DESTINATION
@@ -126,8 +126,8 @@ if(opencoarrays_aware_compiler)
   add_mpi_test(co_min 4 ${tests_root}/unit/collectives/co_min_test)
   add_mpi_test(co_max 4 ${tests_root}/unit/collectives/co_max_test)
   add_mpi_test(syncall 32 ${tests_root}/unit/sync/syncall)
-  add_mpi_test(syncimages 32 ${tests_root}/unit/sync/syncimages)  
-  add_mpi_test(co_reduce 4 ${tests_root}/unit/collectives/co_reduce_test)  
+  add_mpi_test(syncimages 32 ${tests_root}/unit/sync/syncimages)
+  add_mpi_test(co_reduce 4 ${tests_root}/unit/collectives/co_reduce_test)
 #  add_mpi_test(syncimages_status 32 ${tests_root}/unit/sync/syncimages_status)
 
   # Integration tests verifying the use of libcaf_mpi in applications

CheckFortranSourceCompiles.cmake

@@ -38,11 +38,11 @@
 #
 # * Redistributions of source code must retain the above copyright
 # notice, this list of conditions and the following disclaimer.
-# 
+#
 # * Redistributions in binary form must reproduce the above copyright
 # notice, this list of conditions and the following disclaimer in the
 # documentation and/or other materials provided with the distribution.
-# 
+#
 # * Neither the names of Kitware, Inc., the Insight Software Consortium,
 # nor the names of their contributors may be used to endorse or promote
 # products derived from this software without specific prior written

GETTING_STARTED.md

@@ -1,5 +1,5 @@
-[This document is formatted with GitHub-Flavored Markdown.                       ]:# 
-[For better viewing, including hyperlinks, read it online at                     ]:# 
+[This document is formatted with GitHub-Flavored Markdown.                       ]:#
+[For better viewing, including hyperlinks, read it online at                     ]:#
 [https://github.com/sourceryinstitute/opencoarrays/blob/master/GETTING_STARTED.md]:#
 
 # [Getting Started](#getting-started) #
@@ -10,56 +10,56 @@
 
 <a name="the-caf-compiler-wrapper">
 ## The caf compiler wrapper ##
-</a> 
+</a>
 
-The preferred method for compiling a CAF program is by invoking the "caf" bash script 
+The preferred method for compiling a CAF program is by invoking the "caf" bash script
 that the OpenCoarrays CMake scripts install in the "bin" subdirectory of the installation
-path. This is an experimental script with limited but useful capabilities that will 
+path. This is an experimental script with limited but useful capabilities that will
 grow over time.  Please submit bug reports and feature requests via our [Issues] page.
 
 The "caf" script liberates the source code and workflow from explicit dependence on the
-underlying compiler and communication library in the following ways: 
+underlying compiler and communication library in the following ways:
 
 1. With an OpenCoarrays-aware (OCA) CAF compiler, the "caf" script passes the unmodified
-   source code to the underlying compiler with the necessary arguments for building a 
-   CAF program, embedding the paths to OpenCoarrays libraries (e.g., libcaf_mpi.a) installed 
-   in the "lib" subdirectory of the OpenCoarrays installation path.  The "caf" script also 
+   source code to the underlying compiler with the necessary arguments for building a
+   CAF program, embedding the paths to OpenCoarrays libraries (e.g., libcaf_mpi.a) installed
+   in the "lib" subdirectory of the OpenCoarrays installation path.  The "caf" script also
    embeds the path to the relevant module file in the "mod" subdirectory of the installation
    path (e.g., opencoarrays.mod).  This supports use association with module entities via
    ``use opencoarrays``.
-2. With a non-CAF compiler (including gfortran 4.9), "caf" supports a subset of CAF by 
+2. With a non-CAF compiler (including gfortran 4.9), "caf" supports a subset of CAF by
    replacing CAF statements with calls to procedures in the [opencoarrays module] before
-   passing the source code to the compiler.  
+   passing the source code to the compiler.
 
 When using GCC 4.9, we recommend using the `use` statement's "only" clause to
-avoid inadvertent procedure name clashes between OpenCoarrays procedures and their 
+avoid inadvertent procedure name clashes between OpenCoarrays procedures and their
 GCC counerparts.  For example, use "use opencoarrays, only : co_reduce".
 
 With a non-OCA and OCA CAF compilers, the extensions that "caf" imports include the collective
 subroutines proposed for Fortran 2015 in the draft Technical Specification [TS 18508]
 _Additional Parallel Features in Fortran_.
 
-The latter use case provides an opportunity to mix a compiler's CAF support with that of OpenCoarrays.  
-For example, a non-OCA CAF compiler, such as the Cray or Intel compilers, might support all of a 
-program's coarray square-bracket syntax, while OpenCoarrays supports the same program's calls to 
+The latter use case provides an opportunity to mix a compiler's CAF support with that of OpenCoarrays.
+For example, a non-OCA CAF compiler, such as the Cray or Intel compilers, might support all of a
+program's coarray square-bracket syntax, while OpenCoarrays supports the same program's calls to
 collective subroutine such as `co_sum` and `co_reduce`.
 
 <a name="a-sample-basic-workflow">
 ## A sample basic workflow ##
 </a>
 
-The following program listing, compilation, and execution workflow exemplify 
-the use of an OCA compiler (e.g., gfortran 5.1.0 or later) in a Linux bash shell 
-with the "bin" directory of the chosen installation path in the user's PATH 
+The following program listing, compilation, and execution workflow exemplify
+the use of an OCA compiler (e.g., gfortran 5.1.0 or later) in a Linux bash shell
+with the "bin" directory of the chosen installation path in the user's PATH
 environment variable:
 
-      $ cat tally.f90 
+      $ cat tally.f90
       program main
         use iso_c_binding, only : c_int
         use iso_fortran_env, only : error_unit
         implicit none
         integer(c_int) :: tally
-        tally = this_image() ! this image's contribution 
+        tally = this_image() ! this image's contribution
         call co_sum(tally)
         verify: block
           integer(c_int) :: image
@@ -69,7 +69,7 @@ environment variable:
           end if
         end block verify
         ! Wait for all images to pass the test
-        sync all 
+        sync all
         if (this_image()==1) print *,"Test passed"
       end program
       $ caf tally.f90 -o tally
@@ -82,7 +82,7 @@ where "4" is the number of images to be launched at program start-up.
 ## An advanced workflow </a> ##
 
 To extend the capabilities of a non-OCA CAF compiler (e.g., the Intel or Cray compilers),
-access the types and procedures of the [opencoarrays module] by use assocication.  We 
+access the types and procedures of the [opencoarrays module] by use assocication.  We
 recommend using a `use` statement with an `only` clause to reduce the likelihood of a
 name clash with the compiler's native CAf support.  For eample, innsert the following
 at line 2 of `tally.f90` above: