Hi All, OK - I'll hold back until I hear from Damian & Zaak.
Cheers Paul On 27 December 2017 at 21:06, Damian Rouson <dam...@sourceryinstitute.org> wrote: > > Thanks for the additional information Thomas. It sounds like I should test > Paul’s patch. I should be able to do so today and will post the results by > tomorrow. I’m adding OpenCoarrays developer Zaak Beekman to the cc and > attaching the patch again in case he wants to try it as well. > > Zaak, the full thread is at https://gcc.gnu.org/ml/fortran/ and starts with a > message from Paul on November 29. > > Damian > > On December 27, 2017 at 11:09:29 AM, Thomas Koenig > (tkoe...@netcologne.de(mailto:tkoe...@netcologne.de)) wrote: > >> Hi Damian, >> >> > Does breaking binary compatibility simply mean that CAF codes will need to >> > be recompiled (which is fine) >> >> Well... not really. We are not supposed to break binary compatibility >> in a release. For gcc-8, we have greater freedom because we had to >> do it anyway. >> >> Now, the interesting question is the impact. If we break binary >> compatibilty for something that never worked anyway or was useless, or >> something that was broken by a gcc-7 regression, I think we're fine. >> >> If not, well... one possible decision would be to wait for gcc-8 to >> fix this. >> >> > or does it mean that there will need to be work done on OpenCoarrays >> to support the changes >> >> This, I don't know, never having looked at the OpenCoarrays source. >> >> Regards >> >> Thomas -- "If you can't explain it simply, you don't understand it well enough" - Albert Einstein
