New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KokkosBlas::dot is broken for complex, due to incorrect assumptions about Fortran ABI #307
Comments
See this article on the relevant functions: http://mirror.informatimago.com/next/developer.apple.com/hardware/ve/errata.html |
https://www.math.utah.edu/software/c-with-fortran.html#function-return-types "...you should not expect to use Fortran functions that return types such as |
@trilinos/tpetra Patch Trilinos' current snapshot of kokkos-kernels, in order to fix trilinos#3493 and kokkos/kokkos-kernels#307.
My Trilinos PR trilinos/Trilinos#3538 only minimally patches kokkos-kernels to fix this issue. I leave it to the kokkos-kernels developers to figure out the best longer-term approach. However, please do fix this before the next develop-to-master promotion. |
@kyungjoo-kim Can you take care of this please ? |
@crtrott In your dot testing, why do you use the following views ?
In this way, the view is strided and it never tests any tpls as tpls require unit stride according to your ETI design. |
@kyungjoo-kim |
@mhoemmen I know that the standard blas interface has the stride interface but kokkoskernels ETI system instanciates for layoutleft (using unification of layout for 1D view layout right and layout left goes into the instanciated code but the strided case uses kokkos native implementation). |
@crtrott I confused view semantics and thought subview will return stride view. It is all oaky. |
Should be addressed by PR #314, thanks @kyungjoo-kim and @mhoemmen ! |
@trilinos/tpetra Patch Trilinos' current snapshot of kokkos-kernels, in order to fix trilinos#3493 and kokkos/kokkos-kernels#307.
@kyungjoo-kim @crtrott See comment here: trilinos/Trilinos#3493 (comment)
The text was updated successfully, but these errors were encountered: