Bas Nieuwenhuizen
(replying to Bas Nieuwenhuizen)
@hikari That of course assumes ML usecases. MLIR is more general though I'm not sure I've seen anybody use it for something else?
Iwasawa 🌟 (one hikari of too many)
(replying to Bas Nieuwenhuizen)
@bas i'd really like to try using it for non-ML stuff! i kinda dismissed it out of hand the first time i saw it because i wasn't interested in ML stuff at the time, but having learned a bit more about it now, i can appreciate how it might have general applications.
re: bitcode, i'm not surprised, the llvm bitcode is also allegedly a nightmare
1 replies
Bas Nieuwenhuizen
(replying to Iwasawa 🌟 (one hikari of too many))
@hikari yeah, given it's primary usage seems to be machine learning, it is surprising to learn it stand for multi-level IR 🙃
Iwasawa 🌟 (one hikari of too many)
(replying to Bas Nieuwenhuizen)
@bas i appreciate that it doesn't stand for machine learning. it's actually a very fitting name
Iwasawa 🌟 (one hikari of too many)
(replying to Iwasawa 🌟 (one hikari of too many))
@bas re: ONNX, i happen to know quite a bit about it now. the fact it's just protobufs does provide reliable serialisation and deserialisation, it is indeed a nice feature
Iwasawa 🌟 (one hikari of too many)
(replying to Iwasawa 🌟 (one hikari of too many))
@bas oh right the underspecified thing is another thing that applies to LLVM IR too. it's actually infuriating how badly documented that IR is. for MLIR, i don't know, i'm more optimistic about it because of its meta-IR status. i think it'll end up better-documented eventually out of necessity