Improved compilation support for testing

[hiker]

We are getting many different compilation tests in our PSyclone test cases: OpenMP, openacc, opencl (maybe even MPI, though at this stage it appears that this is mostly in the infrastructure library?).

Some of these option need special compiler flags, that might interfere with each other (e.g. can we provide flags for openmp, openacc, and opencl at the same time??), or might need to call a different compiler.

How are we going to support compilation tests in the long term? We obviously don't want to run all test three times (once with openmp, once with openacc, once with opencl).

• Do we want to be able to specify three different compilers and compilation flags (--compiler-openmp, --flags-openmp, ...)?
• Or provide a config file with different set of compiler options?
• Do we want to be able to enable/disable selected compilation tests (e.g. only compile dynamo0p3 code, but not gocean)?
• Or only openmp tests, but nothing else?
• Other options I didn't think of?

I open the discussion here - let's first define what we want to be able to do, then how to conveniently specify this :)

[arporter]

I've come back to this while reviewing #1368 as Aidan is implementing support for OpenMP tasking.

At the moment we only support --compileopencl which enables compilation-testing of OpenCL-specific (Fortran) code. Ideally, we would also support compilation testing with OpenACC and OpenMP enabled (potentially simultaneously but that's not an immediate requirement). Possibly we need a way of specifying that a test should e.g. be tested with OpenMP enabled. A config file for the various options sounds like a good idea as otherwise there's a lot of typing to be done on the command line. However, it would be good to allow the command line to override the config settings if the developer wants to fine-tune a particular option.