You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
flang currently lacks support for assumed-rank dummy arguments like array(..). These are currently required by the following PRIF procedures, and their corresponding Caffeine implementation:
prif_put (non-_raw version only)
prif_get (non-_raw version only)
prif_co_* (all collectives)
This issue suggests creating a temporary (and not officially supported) "dialect" of PRIF and Caffeine, gated by a preprocessor symbol, that entirely omits these features and their corresponding implementation.
To be concrete, this could look something like a -DMISSING_ASSUMED_RANK preprocessor flag added to FPM's C and Fortran flags, and corresponding #if !MISSING_ASSUMED_RANK guards around the declarations and code corresponding to the features above.
Having this in-place should enable us to add flang into CI and test future PRIF PRs submitted against LLVM, which makes this high-priority.
The text was updated successfully, but these errors were encountered:
flang currently lacks support for assumed-rank dummy arguments like
array(..)
. These are currently required by the following PRIF procedures, and their corresponding Caffeine implementation:prif_put
(non-_raw
version only)prif_get
(non-_raw
version only)prif_co_*
(all collectives)This issue suggests creating a temporary (and not officially supported) "dialect" of PRIF and Caffeine, gated by a preprocessor symbol, that entirely omits these features and their corresponding implementation.
To be concrete, this could look something like a
-DMISSING_ASSUMED_RANK
preprocessor flag added to FPM's C and Fortranflags
, and corresponding#if !MISSING_ASSUMED_RANK
guards around the declarations and code corresponding to the features above.Having this in-place should enable us to add flang into CI and test future PRIF PRs submitted against LLVM, which makes this high-priority.
The text was updated successfully, but these errors were encountered: