-
Notifications
You must be signed in to change notification settings - Fork 15k
[mlir] Fix node numbering order in SliceMatchers example #155684
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
Conversation
@llvm/pr-subscribers-mlir Author: Denzel-Brian Budii (chios202) ChangesAfter reviewing this again, it looks like I missed some nodes. Full diff: https://github.com/llvm/llvm-project/pull/155684.diff 1 Files Affected:
diff --git a/mlir/include/mlir/Query/Matcher/SliceMatchers.h b/mlir/include/mlir/Query/Matcher/SliceMatchers.h
index 7181648f06f89..e291bf76e09ef 100644
--- a/mlir/include/mlir/Query/Matcher/SliceMatchers.h
+++ b/mlir/include/mlir/Query/Matcher/SliceMatchers.h
@@ -36,7 +36,7 @@
/// 9
///
/// Assuming all local orders match the numbering order:
-/// {5, 7, 6, 8, 9}
+/// {1, 5, 6, 7, 6, 8, 9}
namespace mlir::query::matcher {
template <typename Matcher>
|
41d01a7
to
985ff92
Compare
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/138/builds/18358 Here is the relevant piece of the build log for the reference
|
After reviewing this again, it looks like I missed some nodes. Node 7 uses node 1 and 5 as well.