Joerg Henrichs
Joerg Henrichs
An MPI compiler wrapper should be independent of the underlying compiler (but obviously use the compiler specific flags). Best approach seems to be dynamically add mpi wrapper: if compiler `X`...
With #309 in progress, we need to implement a way to allow users to specify their own tools. Suggested approach: 1. TBH, the fine-grained tool categories (fcm ,git, subversion etc...
ATM, in `tools/psyclone.py`, we have to use: ``` if TYPE_CHECKING: # Otherwise we have a circular dependency: # BuildConfig needs ToolBox which imports __init__ which imports this from fab.build_config import...
ATM (and with #311) coming in, there is no consistent way of handling flags - some were added in #311 which do not allow path-specific flags (mostly to keep the...
If you build a `.a` file, then modify one source file and rebuild, the `.a` will contain both versions of the compiled files, e.g.: ``` $ ar t ./most.a Constants.2de2473b7.o...
This PR adds configuration settings that enable/disable MPI and OpenMP to BuildConfig. This means that an application can now specify that it should be compiled with OpenMP, without having to...
@MatthewHambley , while working on some linker improvements, we realised that it would be convenient to use shell syntax in some compiler- and linker-flags, e.g.: ``` mpif90 ... $(nf-config --fflags)...
During optimisation (including profiling runs), I ended up using three or four different versions of a transformation script (`original and with tiling` and `profile and non_profile`). This makes it sometimes...
Adds checking if kernel arguments are in a (user-specified) range. This PR consistently renames the old nan_check to value_range_check, including examples, tutorial.
ATM, jinja 2 is only an optional dependency (used with extra dependency 'psydata' only). Given the usefulness (I hope) of ValueRangeCheck (which requires jinja), would it make sense to make...