-
Notifications
You must be signed in to change notification settings - Fork 26
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
More flexible kernel selection #37
Merged
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
fcd2266
FEAT: Add associated constants MR/NR for kernels
bluss 0d652e7
FEAT: Add GemmSelect
bluss 15c18e6
FEAT: Use separate GemmKernel impls for sgemm implementations
bluss b2a582a
MAINT: In travis, print all target features that can be used in script
bluss c3c7e2b
FEAT: Use separate GemmKernel impls for dgemm implementations
bluss a1b88db
FIX: Don't unroll loop4 in debug builds
bluss d1986fd
FEAT: In dgemm sse2 and fallback, use a 4x4 kernel
bluss eaab791
FEAT: In sgemm sse2 and fallback, use a 8x4 kernel
bluss a342d8b
FEAT: Add ConstNum for simple type level integers
bluss 9753437
FEAT: Use type parameter for size in pack
bluss c71f07f
FIX: move kernel-specific constants into each kernel function
bluss 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 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 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
Oops, something went wrong.
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 get this is only for reporting? There is no need to
cargo build
with-Ctarget-cpu=native
hereafter, as those are only for compile time optimization?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.
Yes this is just for reporting, so we can see what kind of machine the travis test is running on!
I'm not that interested in
-Ctarget-cpu=native
at the moment, since we now use runtime target feature detection to deliver good performance by default instead. I keep an eye on that performance doesn't regress if the user supplies-Ctarget-cpu=native
.