Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This just adds declarations for additional compilers:
And also supports the Cray compiler wrapper: on a Cray system, the compilers are always called cc/ftn - but these are just wrappers that (depending on the loaded modules) will execute either the corresponding gnu, intel, or gnu tool (with additional parameters to automatically link libraries like MPI based on the modules loaded.
Since I didn't want to define Ftn and Cc as compiler wrapper (while ftn is pretty much cray specific, cc is definitely very common and would result in confusion), I have therefore names the compiler wrapper
CrayFtn
andCrayCc
(which will be used to create the compiler wrapper for intel and gnu, e.g. with the namescrayftn-ifort
, orcraycc-gcc
).The actual 'native' compiler are only called using the wrapper script, so in order to have a consistent naming scheme, I used the corresponding names
crayftn-ftn
andcraycc-cc
- and the classes are namesCrayftn
andCraycc
. That's a bit confusing (given thatCrayFtn
etc are wrapper), but it was the best idea I had to use class names and compiler (wrapper) names consistently.Better ideas are welcome :)