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
fails for array contexts that do not have the mpi_communicator attribute, but do pass a comm_tag. MIRGE-Com does this when it calls interior_trace_pairs, for example here:
I've started putting some work towards this (#233) before realizing that this is all thoroughly pointless: Eager grudge can only have communication for one tag pending at the same time, otherwise it would deadlock. Therefore, all ranks must hit eager communication in the same order, and so we can do with these tags whatever we want; it won't matter until we allow multiple communications to be pending at the same time.
cc @matthiasdiener
The text was updated successfully, but these errors were encountered: