This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Ping : [Patch, fortran] PR48298 - [F03] User-Defined Derived-Type IO (DTIO)
- From: Andre Vehreschild <vehre at gmx dot de>
- To: Janne Blomqvist <blomqvist dot janne at gmail dot com>
- Cc: Paul Richard Thomas <paul dot richard dot thomas at gmail dot com>, "fortran at gcc dot gnu dot org" <fortran at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>, jerry DeLisle <jvdelisle at charter dot net>, Damian Rouson <damian at sourceryinstitute dot org>, Ian Chivers <ian dot chivers at chiversandbryan dot co dot uk>, Jane Sleightholme <jane at fortranplus dot co dot uk>
- Date: Mon, 29 Aug 2016 10:15:58 +0200
- Subject: Re: Ping : [Patch, fortran] PR48298 - [F03] User-Defined Derived-Type IO (DTIO)
- Authentication-results: sourceware.org; auth=none
- References: <CAGkQGiKvbLD8azLWWaxMSSpSXWb_qHWFFA3=MwG8VFK+-mZ+wg@mail.gmail.com> <CAO9iq9GgiWfta1xDMGo4YT4jShHGKRV0BcfnkTdr42qz4Vvhmg@mail.gmail.com>
Hi all,
> Anyway, a small nit I found was the function st_set_nml_var in
> libgfortran. This is an exported function, and thus part of the ABI.
> So you cannot add arguments to it, as that would break backwards
> compatibility.
Please explain the above. I was of the opinion, that when we change
something significantly the global ABI version gets bumped. Given that
we are doing gcc-7 currently and there have been some changes, that ABI
version should have been bumped already with respect to gcc-6. IMO the
library can't be linked to old objects that use the original
st_set_nml_var() signature anyway. So when there are no other users of
st_set... then why not replace the function signature by a more
suitable one? Or is this function still in use?
I am asking that stupid question mostly, because during extending
coarray stuff to support allocatable components in derived typed
coarrays the API of the caf-library has to be modified and carrying
along the old signatures just causes useless garbage being carried
forward. (Opencoarrays is working on supporting the same renovated API.
Other users of that API are not known to me.) So what is the best way
to resolve this?
- Andre
--
Andre Vehreschild * Email: vehre ad gmx dot de