[Mlir-commits] [mlir] [mlir][x86vector] Sink Vector.transfer_reads and vector.load before the consumer (PR #169333)

[Renato Golin]

https://github.com/rengolin approved this pull request.

I now understand the original point, sorry it took so long. You check the "next" operation because if may have already moved "before" (in a previous iteration) and now they're "guaranteed" to be next to each other in program order if they have the same "first" user.

Let's get this merged, as it's good to go now. Once/IF we move this to a more generic place (ex. the vector dialect), we can reevaluate the approach.

https://github.com/llvm/llvm-project/pull/169333