https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120958
--- Comment #17 from Richard Biener <rguenth at gcc dot gnu.org> --- I had the impression we are talking about a legacy (F77) code base here and we need to honor the constraints of that language. That means limited ways to express inter-operability with C and thus from a QOI perspective we shouldn't break such code so I agree with Harald here. For F77 we need to default to a behavior that's safe and that worked the last 20 years with gfortran. The ability to know that bar() cannot modify x is new, so there's not much of a regression to be had compared to 20 years ago. I'm less sure about F90, F20xy - do all of them have the ability to specify the async MPI behavior correctly?
