-
Notifications
You must be signed in to change notification settings - Fork 11
(feat): Add a straightforward implementation for tile iterator. #50
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
6020263
Add a straightforward implementation for tile iterator.
haruhi55 b7bb0e5
refine the implementation.
haruhi55 6895977
refine interfaces for copy from shared to register.
haruhi55 3f67f84
fix disordered includes.
haruhi55 f80c65b
clean include relations.
haruhi55 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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 was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder why such modifications are necessary in order for it to compile successfully?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The include order in
copy/mod.hpp
is as follows:TiledCUDA/include/cell/copy/mod.hpp
Lines 3 to 5 in b31db2a
copy/copy.hpp
is beforedyn_copy.hpp
.copy.hpp
includes<cute/algorithm/copy.hpp>
:TiledCUDA/include/cell/copy/copy.hpp
Line 5 in b31db2a
and
dyn_copy.hpp
include<cute/tensor.hpp>
TiledCUDA/include/cell/copy/dyn_copy.hpp
Line 5 in b31db2a
In a conclusion,
<cute/algorithm/copy.hpp>
is included before<cute/tensor.hpp>
. When I upgrade g++ into 10.5.0., it complains that:Similar issues can be found in: NVIDIA/cutlass#1508 and NVIDIA/cutlass#1484
I am not sure why the compilation is successful in g++ 9.4.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems this might be a bug in CuTe, where they haven't handled the dependencies between header files very well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So does that mean when using copy-related functions later, we won't be able to directly include all the copy-related header files, but can only include one specific header file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect things won't be that bad. I suggest leaving this PR to be merged later. I can examine the include order to make it clearer.