ergawy wrote: @kiranchandramohan @clementval thanks for your comments (and sorry for the late response, I was off yesterday).
Sure, we can works on a multi-range loop op in FIR, our team did not write the current loop op definition so I was working with what I have. Just to be on the same page, do you suggest to have a separate op for `do concurrent` (separate from the current `fir.do_loop` op)? Or extend the current to model: - multi-range iteration - and multi-block loop bodies? I am leaning towards extending the current op to be more capable/flexible but if you have any reasons not to do so, please let me know. In any case, there is not problem blocking this PR until we can model multi-range loops (at least, maybe we can defer multi-block loops to a later point). https://github.com/llvm/llvm-project/pull/127595 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
