In the overwhelmingly majority of cases only one dialect is generated at a time
anyways, and this restriction more easily catches user error when multiple
dialects might be generated. We hit this semi-recently with the PDL dialect,
and circt+other downstream users are also actively hitting this as well.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Thanks, and yes with Marius 's change for doc includes (couple months back :-)) there isn't really reason to have multiple be generated website side. Being explicit here is better.
Did none of the cmake files need to change? If I'm reading this change correctly it just bails out if no dialect is specified, and so I'd expect some to fail (well except if the default cmake config already does set this flag)
It bails if no dialect is specified and there isn't a single dialect (which matches the dialectgen handling). We realistically could always enforce the flag, but I'd need to update uses of dialect gen as well.
I had to update a couple, which conveniently looked alright on the website only because the main dialect was alphabetically ordered before the one that got included. I'll try to see if in a follow up we can roll this into add_mlir_dialect, to handle all of this automatically.