Am 18.02.25 um 16:00 schrieb Andre Vehreschild:
Hi Thomas,
This patch series (of necessity) introduces ABI changes. What will
happen with user code compiled against the old interface?
That depends on the library you are linking against. When using caf_single from
gfortran, then you will get link failures when you mix code compiled by
gfortran < 15 and gfortran-15. But caf_single is anyhow only considered for
testing. So why should one do this ?
OK.
If your questions targets the users of this ABI, which to my knowledge is only
OpenCoarrays at the moment, then the user will experience nothing. A mix of
pre-gfortran-15 and gfortran-15 generated .o-files will link and work as
expected, because OpenCoarrays provides all ABIs. We do not compile a
gfortran-15 exclusive version of OpenCoarrays, i.e. all routines are present,
fully functional and interoperable.
Very good, then.
I guess a link failure (plus an answer in stack exchange where the
explanation is given, so people can google it, and a mention in the
release notes) would be acceptable, but is there anything that
can be done in addition?
I can provide an entry in release notes, if need be. Where do I have to do
this? Never did.
It is a separate repository from the gcc source, it can be found by
cloning git+ssh://you...@gcc.gnu.org/git/gcc-wwwdocs.git .
Best regards (and a lot of thanks for the patch series!)
Thomas
