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.
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
[mlir][linalg] Vectorization support for convolution of i1 type #109480
base: main
Are you sure you want to change the base?
[mlir][linalg] Vectorization support for convolution of i1 type #109480
Changes from 1 commit
e5fc941
6f839f3
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Could you adopt one of the existing tests for
linalg.conv_1d_ncw_fcw
instead? And move this next to the original example that you would adopt? Thanks! This way it will be much easier to see all the cases that are tested for a particular Op. Also, it would be good to add a few more examples fori1
.IIUC, the only difference between
i1
and e.g.i32
would be the combining Op invector.contract
? If that's the case, then IMHO you can write rather reducedCHECK
lines that primarily verify the contract Op. Everything else should be identical to what we get today fori32
, right? As per https://mlir.llvm.org/getting_started/TestingGuide/:There's obviously room for interpretation and having more
CHECK
lines is also totally fine :)