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

[MLIR][affine] Proper handling of vector load / stores in Affine dialect and transformations #115989

Open
dragondracarys007 opened this issue Nov 13, 2024 · 4 comments
Labels
good first issue https://github.com/llvm/llvm-project/contribute mlir:affine

Comments

@dragondracarys007
Copy link

In the context of Issue-115849 , I see that affine transformation is producing invalid IR like below where vector is being stored to a memref of size 1x1xf32.

`affine.vector_store %5, %alloc[0, 0] : memref<1x1xf32>, vector<64x64xf32>

%6 = affine.vector_load %alloc[0, 0] : memref<1x1xf32>, vector<64x512xf32>`

I think validity of the affine transformations need to be enhanced by introducing good verifiers.

@llvmbot
Copy link

llvmbot commented Nov 13, 2024

@llvm/issue-subscribers-mlir-affine

Author: None (dragondracarys007)

In the context of [Issue-115849](https://github.com//issues/115849) , I see that affine transformation is producing invalid IR like below where vector is being stored to a memref of size 1x1xf32.

`affine.vector_store %5, %alloc[0, 0] : memref<1x1xf32>, vector<64x64xf32>

%6 = affine.vector_load %alloc[0, 0] : memref<1x1xf32>, vector<64x512xf32>`

I think validity of the affine transformations need to be enhanced by introducing good verifiers.

@bondhugula bondhugula added the good first issue https://github.com/llvm/llvm-project/contribute label Nov 15, 2024
@llvmbot
Copy link

llvmbot commented Nov 15, 2024

Hi!

This issue may be a good introductory issue for people new to working on LLVM. If you would like to work on this issue, your first steps are:

  1. Check that no other contributor has already been assigned to this issue. If you believe that no one is actually working on it despite an assignment, ping the person. After one week without a response, the assignee may be changed.
  2. In the comments of this issue, request for it to be assigned to you, or just create a pull request after following the steps below. Mention this issue in the description of the pull request.
  3. Fix the issue locally.
  4. Run the test suite locally. Remember that the subdirectories under test/ create fine-grained testing targets, so you can e.g. use make check-clang-ast to only run Clang's AST tests.
  5. Create a Git commit.
  6. Run git clang-format HEAD~1 to format your changes.
  7. Open a pull request to the upstream repository on GitHub. Detailed instructions can be found in GitHub's documentation. Mention this issue in the description of the pull request.

If you have any further questions about this issue, don't hesitate to ask via a comment in the thread below.

@llvmbot
Copy link

llvmbot commented Nov 15, 2024

@llvm/issue-subscribers-good-first-issue

Author: None (dragondracarys007)

In the context of [Issue-115849](https://github.com//issues/115849) , I see that affine transformation is producing invalid IR like below where vector is being stored to a memref of size 1x1xf32.

`affine.vector_store %5, %alloc[0, 0] : memref<1x1xf32>, vector<64x64xf32>

%6 = affine.vector_load %alloc[0, 0] : memref<1x1xf32>, vector<64x512xf32>`

I think validity of the affine transformations need to be enhanced by introducing good verifiers.

@bondhugula
Copy link
Contributor

In this case, the transformation that generated invalid IR shouldn't have happened in the first place. I seehttps://github.com//issues/115849 as an instance of this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue https://github.com/llvm/llvm-project/contribute mlir:affine
Projects
None yet
Development

No branches or pull requests

4 participants