[mlir][memref] Fix typo in BuiltinAttributeInterfaces description
#136774
Conversation
|
Thank you for submitting a Pull Request (PR) to the LLVM Project! This PR will be automatically labeled and the relevant teams will be notified. If you wish to, you can add reviewers by using the "Reviewers" section on this page. If this is not working for you, it is probably because you do not have write permissions for the repository. In which case you can instead tag reviewers by name in a comment by using If you have received no comments on your PR for a week, you can request a review by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate is once a week. Please remember that you are asking for valuable time from other developers. If you have further questions, they may be answered by the LLVM GitHub User Guide. You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums. |
|
@llvm/pr-subscribers-mlir-ods Author: Aleksandar Zecevic (azecevicTT) ChangesFull diff: https://github.com/llvm/llvm-project/pull/136774.diff 1 Files Affected:
diff --git a/mlir/include/mlir/IR/BuiltinAttributeInterfaces.td b/mlir/include/mlir/IR/BuiltinAttributeInterfaces.td
index 6220d80264bdf..6cf8729b92c83 100644
--- a/mlir/include/mlir/IR/BuiltinAttributeInterfaces.td
+++ b/mlir/include/mlir/IR/BuiltinAttributeInterfaces.td
@@ -480,8 +480,8 @@ def MemRefLayoutAttrInterface : AttrInterface<"MemRefLayoutAttrInterface"> {
Note: the MemRef type's layout is assumed to represent simple strided buffer
layout. For more complicated case, like sparse storage buffers,
- it is preferable to use separate type with more specic layout, rather then
- introducing extra complexity to the builtin MemRef type.
+ it is preferable to use a separate type with a more specific layout, rather
+ than introducing extra complexity to the builtin MemRef type.
}];
let methods = [
|
|
@llvm/pr-subscribers-mlir Author: Aleksandar Zecevic (azecevicTT) ChangesFull diff: https://github.com/llvm/llvm-project/pull/136774.diff 1 Files Affected:
diff --git a/mlir/include/mlir/IR/BuiltinAttributeInterfaces.td b/mlir/include/mlir/IR/BuiltinAttributeInterfaces.td
index 6220d80264bdf..6cf8729b92c83 100644
--- a/mlir/include/mlir/IR/BuiltinAttributeInterfaces.td
+++ b/mlir/include/mlir/IR/BuiltinAttributeInterfaces.td
@@ -480,8 +480,8 @@ def MemRefLayoutAttrInterface : AttrInterface<"MemRefLayoutAttrInterface"> {
Note: the MemRef type's layout is assumed to represent simple strided buffer
layout. For more complicated case, like sparse storage buffers,
- it is preferable to use separate type with more specic layout, rather then
- introducing extra complexity to the builtin MemRef type.
+ it is preferable to use a separate type with a more specific layout, rather
+ than introducing extra complexity to the builtin MemRef type.
}];
let methods = [
|
|
@llvm/pr-subscribers-mlir-core Author: Aleksandar Zecevic (azecevicTT) ChangesFull diff: https://github.com/llvm/llvm-project/pull/136774.diff 1 Files Affected:
diff --git a/mlir/include/mlir/IR/BuiltinAttributeInterfaces.td b/mlir/include/mlir/IR/BuiltinAttributeInterfaces.td
index 6220d80264bdf..6cf8729b92c83 100644
--- a/mlir/include/mlir/IR/BuiltinAttributeInterfaces.td
+++ b/mlir/include/mlir/IR/BuiltinAttributeInterfaces.td
@@ -480,8 +480,8 @@ def MemRefLayoutAttrInterface : AttrInterface<"MemRefLayoutAttrInterface"> {
Note: the MemRef type's layout is assumed to represent simple strided buffer
layout. For more complicated case, like sparse storage buffers,
- it is preferable to use separate type with more specic layout, rather then
- introducing extra complexity to the builtin MemRef type.
+ it is preferable to use a separate type with a more specific layout, rather
+ than introducing extra complexity to the builtin MemRef type.
}];
let methods = [
|
No description provided.