Skip to content
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

cutlass update #18

Merged
merged 11 commits into from
May 7, 2024
Merged

cutlass update #18

merged 11 commits into from
May 7, 2024

Conversation

Shreya-gaur
Copy link

No description provided.

@Shreya-gaur Shreya-gaur self-assigned this Jul 17, 2023
@Shreya-gaur Shreya-gaur linked an issue Jul 17, 2023 that may be closed by this pull request
Copy link

@JRPan JRPan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

take out .github folder
Also resolve the merge conflict.

@Shreya-gaur Shreya-gaur requested review from JRPan and removed request for tgrogers July 20, 2023 16:09
@JRPan
Copy link

JRPan commented Sep 15, 2023

@Shreya-gaur Could you please resolve the merge conflict? Thanks. I don't know why it's here again tho.

@tgrogers
Copy link
Contributor

@Shreya-gaur - can we change the way we integrate cutlass?
Instead of copying all the code here, can we just sync the folder to a particular commit number of their public repo?
We do something similar with heterosync:

# Maybe we should use submodules for this - but I have heard a lot of horor stories about these..

We would still need your changes to Make, etc, but unless we are making changes to the cutlass code, I see no reason to duplicate it all here.

@William-An William-An merged commit 63f97ac into accel-sim:dev May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update Cutlass Version
4 participants