Yes, that's the correct MLIR way of passing attributes to LLVM.

Fix empty strides assertion error

Address comments

Rebased

Rebased

I think it's ok as a fallback for f16/f32, but maybe @mehdi_amini has a different opinion.

Upd

It will lead to slightly slower startup times, but we can always switch to deferred sorting if that is a problem. (It isn't clear how much it matters in practice anyways).

In D118937#3294739, @rriddle wrote:

Do you have an idea on the cost of this vs. say computing on demand?

I get this error locally:

Can you please also add tests cases to tests (benchmarks?) in this folder: https://github.com/llvm/llvm-project/tree/main/mlir/test/Integration/Dialect/Async/CPU

thank you! For our MLIR use case this is exactly what we need.

Rebase

Fix bugs

There are two places where in MLIR you can put an attribute to coroutine functions:

Build is failing: https://buildkite.com/llvm-project/premerge-checks/builds/70123#b97ba1d4-10ba-4287-899a-0bcf5260aefe