Re:The Rust Calling Convention We Deserve
by jcranmer on Thursday April 18, 2024 @09:05PM
(#40082429)
> Can someone explain simply where does MLIR fit into all of this?
It doesn't.
MLIR is a design for a family of intermediate languages (called 'dialects') that allow you to progressively lower high-level languages into low-level code.
The ML media cycle is so unhinged that I've seen people simply assume out of hand that MLIR stands for Machine Learning Intermediate Representation.
Re:The Rust Calling Convention We Deserve
by fpgamlirfanboy on Thursday April 18, 2024 @09:50PM
(#40082714)
> Side-note: Mojo has been designed by the creator of LLVM and MLIR to prioritize and optimize vector hardware use, as a language that is similar to Python (and somewhat syntax compatible).
Are people getting paid to repeat this ad nauseum?
Re:The Rust Calling Convention We Deserve
by jadodev on Thursday April 18, 2024 @10:28PM
(#40082900)
MLIR includes a "linalg" dialect that contains common operations.
You can see those here: https://mlir.llvm.org/docs/Dialects/Linalg/
This post is rather unrelated. The linalg dialect can be lowered to LLVM IR, SPIR-V, or you could write your own pass to lower it to e.g. your custom chip.
Can someone explain simply where does MLIR fit into all of this? Does it standardize more advanced operations across programming languages - such as linear algebra and convolutions?
Side-note: Mojo has been designed by the creator of LLVM and MLIR to prioritize and optimize vector hardware use, as a language that is similar to Python (and somewhat syntax compatible).