Add P3222R0: "Fix C++26 by adding transposed special cases for P2642 layouts" #454
Conversation
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
nmm0
reviewed
Apr 2, 2024
and improve explanations.
mhoemmen
changed the title
transposed special cases for P2642 layouts"
mhoemmen
changed the title
transposed special cases for P2642 layouts"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I've already submitted this for the 2024/04/16 mailing.
Abstract:
We propose to change the C++ Working Paper so that
linalg::transposedincludes special cases forlayout_left_paddedandlayout_right_padded. These are the two mdspan layouts proposed by P2642R6, which was voted into the C++ Working Draft at the Tokyo 2024 WG21 meeting. This change will make it easier forlinalgimplementations to optimize for these two layouts by dispatching to an existing optimized C or Fortran BLAS. Delaying this until after C++26 would be a breaking change.Fixes #448