Welcome to the 52th issue of the MLIR Newsletter covering developments in MLIR, and related projects in the ecosystem. We welcome your contributions (contact: javed.absar@gmail.com). Click here to see previous editions.
Highlights
-
US LLVM Dev Santa Clara, CA on October 10-12, 2023. Call for Speakers Deadline extended.
-
This week LLVM-Weekly celebrated its 500th edition. Thanks Alex Bradbury for amazing commitment and service to the community. [LLVM Weekly].
-
Mehdi posted [RFC] MLIR with respect to LLVM releases - MLIR - LLVM Discussion Forums.
-
Maksim started thread to collect up all the confusing MLIR error messages people stumble over [thread].
MLIR Commits
-
Cullen Rhodes shared an update on ArmSME dialect and proposed next steps - MLIR - LLVM Discussion Forums. Also follow-up Loop materialization in ArmSME - MLIR - LLVM Discussion Forums.
-
Matthias Springer: Use DenseI64ArrayAttr for ExtractOp/InsertOp positions rather than I64ArrayAttr.
-
Thomas Raoux: Fixed arith ops verifier for tensor with encoding.
-
Martin fixed memory leak possibility in Bufferizer [canonicalizer to remove duplicate values].
-
Mehdi Amini added [added an MLIR example of some mimimal example of MLIR setup] which may serve as example and showcase of the MLIR binary footprint.
-
Alex Zinenko: “Linalg structure ops do not implement control flow in the way expected by RegionBranchOpInterface, and the interface implementation isn’t
actually used anywhere. The presence of this interface without correct
implementation is confusing for, e.g., dataflow analyses”. [commit].
MLIR RFC Discussions
-
Question on Interface method body - Discord …“the intent of the method body is to dispatch the call to the interface method differently than calling the derived function with the same name (which is what the method body generated by ODS does by default)”
-
A utility class to get or create instances of “storage classes”. MLIR: mlir::StorageUniquer Class Reference.
Useful Links