From: Dave Love <dave.love@manchester.ac.uk>
To: fortran@gcc.gnu.org
Subject: backwards incompatibility
Date: Mon, 12 Mar 2018 15:40:00 -0000 [thread overview]
Message-ID: <871sgp8fpb.fsf@albion.it.manchester.ac.uk> (raw)
It's quite a pain for supporting research systems that the gfortran
module format changes incompatibly with every (?) new version. For
instance, you can't mix development packages built with the RHEL system
compiler with the more recent "devtoolset" compiler needed for hardware
support. As far as I know, the proprietary compilers don't have the
same issue. I can't find anything written about that, but I haven't
tried to understand the implementation. Is there something written?
Otherwise, is it feasible to convert older module files to newer
formats, given that the ABI doesn't change, as I've seen in release
notes (and would hope)? If so, where would one look in the code to see
about doing so?
Version 8 makes the situation worse by breaking run time compatibility,
not just build-time, with a different libgfortran shared library
version. That already caused considerable disruption with Fedora
packaging after the switch to GCC 8. With ELF, can't you use versioned
symbols to avoid a new soname, like libgcc and libgomp do?
Regardless of any annoyances, thanks for keeping a competitive free
compiler going!
next reply other threads:[~2018-03-12 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 15:40 Dave Love [this message]
2018-03-12 17:05 ` Steve Kargl
2018-03-12 20:42 ` Dave Love
2018-03-12 21:18 ` Thomas Koenig
2018-03-13 15:14 ` Dave Love
2018-03-14 2:31 ` Jerry DeLisle
2018-03-16 13:48 ` Dave Love
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=871sgp8fpb.fsf@albion.it.manchester.ac.uk \
--to=dave.love@manchester.ac.uk \
--cc=fortran@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).