GPU_FUNC_TERM and GPU_FUNC_TERM_WITH_RETURN usage confuses clang-format
These macros are used in headers that are included for both GPU and non-GPU builds to alternately define easily-inlined dummy functions or to declare optional GPU code paths. This means they may expand to either
; and the macro must be expanded to have a well-formed C++ expression, which clang-format evidently does not do. See comments in https://gerrit.gromacs.org/c/gromacs/+/12300
Options include refactoring these constructs and code dispatching, but plausible quick fixes include adding potentially redundant/unnecessary
; to such usages.