-
Notifications
You must be signed in to change notification settings - Fork 1.4k
cuda : deterministic and faster k_copy_src1_to_contiguous #1179
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
Closed
Closed
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
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
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.
Please also link the PRs from which the code has been taken.
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.
Please note that the
ggmlprojects track copyrights through the git history, which is a more accurate mechanism than having copyright notices in the source code. The latter becomes obsolete very quickly, while the git commit history preserves information about the specific changes and the process is fully automated. Therefore the recommended way to register a copyright when upstreaming code to the projects is by setting the correct author of the patches. See ggml-org/llama.cpp#6405 for more information.Just wanted to make sure that you understand that these notices are redundant and the maintainers will not be responsible to preserve them with time. Also would like to make it explicitly clear - the presence of such notices in the code will not prevent usage of the referenced code in other parts of the codebase, regardless if the copyright holder agrees or not. One of the main goals to have an MIT-based project is to be able to work in a collaboration that freely allows to share and apply ideas among all contributors and parts of the codebase. The origins of an idea can be accurately tracked through the commit history and the AUTHORS file clearly notifies about all copyright holders of the project.
Linking original PRs is fine.
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 was thinking more along the lines of just documenting where the code comes from since otherwise the copyright notices would be confusing. I did not intend to comment on how and where copyright notices are acceptable.
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.
According to the MIT license I'm obligated to preserve the copyright notice when there is one, while this does not apply here since the downstream file didn't happen to have one I think I'm nevertheless going to insist this time.
Subsequent PRs will be based off files that do have it, so as far as the license goes I don't think we have a choice. When/if the affected code goes away or gets significantly altered by someone else I don't see a problem with modifying/removing the notice as fit.
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.
Including copyright notices is optional since the Berne convention - this was discussed last year: ggml-org/llama.cpp#6394.
And again - we do provide the notices in the AUTHORS files. There is no need to sprinkle them inside the code.