Hi Thomas, That's a good question. I have kept Damian in copy. It must be said that the OpenCoarray folk are more concerned with PR83319, where there is no problem of binary compatibility. I am awaiting some input from him.
Cheers Paul On 27 December 2017 at 17:50, Thomas Koenig <tkoe...@netcologne.de> wrote: > Hi Paul, > >> It will break binary compatibility for caf with scalar, >> allocatable/pointer components. This comes about because I decided >> that the caf tokens for thes components, should come after all other >> components, rather than immediately after the "owner" component. This >> has the advantage, that they are then binary compatible with external >> functions or modules that are not compiled with -fcoarray = lib. > > > So, is this something that we can do for gcc-7 (where we shold maintain > binary compatibility)? > > Regards > > Thomas -- "If you can't explain it simply, you don't understand it well enough" - Albert Einstein