We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
[[no_unique_address]]
In config.hpp there are these checks for using [[no_unique_address]] or using an emulation of it.
#if !defined(_MDSPAN_USE_ATTRIBUTE_NO_UNIQUE_ADDRESS) # if ((__has_cpp_attribute(no_unique_address) >= 201803L) && \ (!defined(__NVCC__) || MDSPAN_HAS_CXX_20) && \ (!defined(_MDSPAN_COMPILER_MSVC) || MDSPAN_HAS_CXX_20)) # define _MDSPAN_USE_ATTRIBUTE_NO_UNIQUE_ADDRESS 1 # define _MDSPAN_NO_UNIQUE_ADDRESS [[no_unique_address]] # else # define _MDSPAN_NO_UNIQUE_ADDRESS # endif #endif
Using of [[no_unique_address]] is disabled if it's compiled by nvcc. Is this just because this was not supported by nvcc at some point?
Current nvcc does support it now (as long as the host compiler supports it).
The text was updated successfully, but these errors were encountered:
There were also issues with working slightly different on host and device, and that leading to mismatched sizes.
Sorry, something went wrong.
Merge pull request kokkos#198 from kokkos/Fix-196-mac-clang-13-build
4d2601a
Add missing include to fix Mac clang-13 build
No branches or pull requests
In config.hpp there are these checks for using
[[no_unique_address]]
or using an emulation of it.Using of
[[no_unique_address]]
is disabled if it's compiled by nvcc. Is this just because this was not supported by nvcc at some point?Current nvcc does support it now (as long as the host compiler supports it).
The text was updated successfully, but these errors were encountered: