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
the only thing distinguishing those two is how they are stored in the backend, i.e. this is a pure implementation detail which should not have an effect on the default implementation - they should be exactly the same. also there should not be any logic in the expression classes regarding this distinction
The text was updated successfully, but these errors were encountered:
i just realized that this is not the case - at least for the block implementation which can make use of the dense storage. Still, it feels wrong to have a distinction on the level of expressions.
one example of where this fails is when we have C=A % T where T is triangular. The kernels are perfectly capable of doing this via trans(C) = trans(T) % trans(A), however, on expression level this logic is not implemented, so this will fail.
Ulfgard
changed the title
unify tpmv and trmv kernel routines
Rethink triangular matrix handling
Sep 10, 2017
the only thing distinguishing those two is how they are stored in the backend, i.e. this is a pure implementation detail which should not have an effect on the default implementation - they should be exactly the same. also there should not be any logic in the expression classes regarding this distinction
The text was updated successfully, but these errors were encountered: