[Mlir-commits] [flang] [mlir] [flang][OpenMP] Add `OutlineableOpenMPOpInterface` to `omp.teams` (PR #131109)

[Kareem Ergawy]

ergawy wrote:

> Thank you, this makes sense to me. I'm just wondering whether several other operations which don't have this interface should (e.g. `omp.section(s)`, `omp.taskgroup`, `omp.master`, ...), in order to avoid the same issue, or what is the logic to choose when this is needed.

I did not go over other constructs to be honest. But I think this will for sure happen for any outlinable construct that does not have the `OutlineableOpenMPOpInterface` attached to it since the chosen allocation scope will be from some parent op not the op of the construct itself. I came across this working on delayed privatization for `distribute`.

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