Dan Ibanez

@rppawlo did this work or is there something missing in Kokkos for your use case?

I would also like to have a resolution to this, it seems like an inappropriate code smell for the central CMake toolbox at Livermore to be emitting these warnings in...

shouldn't this be something that is addressed in the kokkos/kokkos repository after these headers are merged into it? We can't really develop things on top of Kokkos execution spaces in...

@jeffmiles63 shouldn't #22 be something that is addressed in the kokkos/kokkos repository after these headers are merged into it? We can't really develop things on top of Kokkos execution spaces...

@alanw0 @tasmith4 can you comment on whether all of these are actually needed? I know Sierra/SM has transitioned to the library already.

@alanw0 yea that's the goal here, so we should include things that are somehow provided by the `stk_simd` wrapper layer as well.

@crtrott @bjoo sorry for not seeing this earlier. @crtrott did @bjoo sufficiently address your feedback? If so I can look at merging.

@nmhamster I personally was unaware of that. The way the ISO interface works, we have template specializations called "ABI"s (a bit of misnomer). Some of those "ABI"s are directly calling...

Since this issue was originally about missing pieces to the ISO interface, I'm going to answer the question that @alanphumphrey asked in the other issue because it fits better here....

@nmhamster I have some early data on different high-level approaches using a full and very non-trivial Sandia application built using Clang on Mac: 1. using `float[8]` with `pragma clang loop...