From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: FX Coudert <fxcoudert@gmail.com>
Cc: Tobias Burnus <burnus@net-b.de>,
gcc-patches <gcc-patches@gcc.gnu.org>,
"'fortran@gcc.gnu.org'" <fortran@gcc.gnu.org>
Subject: Re: libgfortran ABI compatibility / stability (was: Re: [patch,fortran] Add -fdump-core option to coredump at library run-time errors (PR29649))
Date: Sat, 06 Jan 2007 17:08:00 -0000 [thread overview]
Message-ID: <20070106170442.GA54793@troutmask.apl.washington.edu> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2007-01-06 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 21:24 [patch,fortran] Add -fdump-core option to coredump at library run-time errors (PR29649) Tobias Burnus
[not found] ` <6113E044-201A-4840-8134-FAE8C096A185@gmail.com>
2007-01-06 10:21 ` Tobias Burnus
2007-01-06 14:48 ` libgfortran ABI compatibility / stability (was: Re: [patch,fortran] Add -fdump-core option to coredump at library run-time errors (PR29649)) FX Coudert
2007-01-06 17:08 ` Steve Kargl [this message]
2007-01-12 6:45 ` [patch,fortran] Add -fdump-core option to coredump at library run-time errors (PR29649) FX Coudert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070106170442.GA54793@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).