[RFC] Restructuring of the MLIR repo

[sjarus]

@clattner

My personal opinion is that Linalg, and the things that depend on it, should be split out of the MLIR repo. It should either go into its own top-level thing, or perhaps into an incubator. It seems like its design is still evolving very rapidly, and I’ve heard a number of people be surprised by this - they thought integration into the MLIR repo implied a bit more stability…

This conversation seems related to what I just posted an RFC about: [RFC] Moving TOSA construction lib into MLIR core . Frontends → TOSA → LinAlg is a functional path, but also one in development. Certain artifacts in TOSA also drove LinAlg-side development, e.g. TOSA to Linalg lowering (tosa.scatter) - #3 by hanchung .

In the quoted RFC I mentioned the problem with testing op constructors for a dialect like TOSA that sits at the interface from multiple frontends. A proposed way to address it is a dummy frontend dialect, but that brings its own share of concerns. It would nice to somehow integrate legalization test harnesses sitting within the real frameworks too.