This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: libgfortran ABI compatibility / stability (was: Re: [patch,fortran] Add -fdump-core option to coredump at library run-time errors (PR29649))
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: FX Coudert <fxcoudert at gmail dot com>
- Cc: Tobias Burnus <burnus at net-b dot de>, gcc-patches <gcc-patches at gcc dot gnu dot org>, "'fortran at gcc dot gnu dot org'" <fortran at gcc dot gnu dot org>
- Date: Sat, 6 Jan 2007 09:04:42 -0800
- Subject: Re: libgfortran ABI compatibility / stability (was: Re: [patch,fortran] Add -fdump-core option to coredump at library run-time errors (PR29649))
- References: <459EC21E.7070204@net-b.de> <EAAF3894-95DB-43B5-9EF4-0C2796D676AE@gmail.com>
On Sat, Jan 06, 2007 at 03:47:52PM +0100, FX Coudert wrote:
> >As set_std is modified, this makes the library incompatible with
> >previously compiled gfortran programs. One should thus either bump the
> >library version or consider to backport it to 4.2. (Suggestions?)
>
> I've been inactive in gfortran devel recently, so I'd like to know
> what is the consensus reached on that point. My own opinion is that
> it's too late for strict 4.2/4.3 ABI compatibility, and also too late
> for backporting the versioning patch to 4.2, so we might as well
> declare 4.3 incompatible with 4.2 & bump the version number.
>
I agree that it is too late to back port to 4.2. This
then suggests that a library version bump is needed.
However, I've never gotten the versioning patch to work
on FreeBSD, and my attempts to fix all failed.
--
Steve