richard.barton.arm added a comment. Option 1 for me, let's not delay.
With upstreaming of fir-dev making great progress, we can start to think about having a working flang in LLVM 15. For that we would need to have upstreaming finished, the driver finished and CMake support finished before end of June. The initial user experience work should be focused on LLVM 15. The sooner we have the code on main branch, the sooner we can begin the work of shaking out the problems. To delay means that flang in LLVM 15 will not be as good as it could be. This patch is orthogonal to the issues discussed on this thread and on the call on 4th April. Anyone using flang today is going to see those issues just the same with or without this patch as flang will error out before it gets to linking. Committing this patch won't change what flang can't do yet but it will probably flush out some more issues - perhaps serious ones - for us to fix. I don't think we should be scared to receive bug reports. At this stage in development, bug reports are surely good for us and the sooner we get them, the sooner we can potentially fix the issues. I think the group of interested users with high quality-level expectations for flang are going to be evaluating it on a release rather than at some random point on main. I think anyone following along on main is going to have an accurate understanding of flang's maturity there and unlikely to be surprised by the quality of it. We should consider asking Alex to skip this patch in LLVMWeekly, or ask him to message it as we want to. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D122008/new/ https://reviews.llvm.org/D122008 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
