Fix array assert compilation failure#297
Merged
psychocoderHPC merged 1 commit intoalpaka-group:devfrom Feb 2, 2026
Merged
Conversation
psychocoderHPC
approved these changes
Feb 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There's an unfortunate compiler compilation that fails to build some standard library code:
Thus, if you try to compile standard library code for device, you might hit those asserts being non-constexpr host-only functions. LLVM >= 21.8.0 has a workaround for this (see there for details, examples, etc.) but the ROCm 6.x.x stack builds on a much older LLVM version.
This PR replaces standard library
spanwith an own constexpr-only implementation of the necessary functionality.