public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jerry DeLisle <jvdelisle@charter.net>
To: fortran@gcc.gnu.org
Subject: Re: backwards incompatibility
Date: Wed, 14 Mar 2018 02:31:00 -0000	[thread overview]
Message-ID: <f4b02d10-0fa7-7fe1-0b13-3d0b0f14b036@charter.net> (raw)
In-Reply-To: <87zi3c57o8.fsf@albion.it.manchester.ac.uk>

On 03/13/2018 08:14 AM, Dave Love wrote:
> Thomas Koenig <tkoenig@netcologne.de> writes:
> 
>> Hi Dave,
>>
>>> It's quite a pain for supporting research systems that the gfortran
>>> module format changes incompatibly with every (?) new version.
>>
>> A lot of releases, yes. The problem is that we use a lot of positional
>> parameters in the files.
>>
>> I have given a little thought of how to get around that by using some
>> sort of keyword-value scheme, which by definition are almost infinitely
>> extensible.
>>
>> Another possibility would be to write out INTERFACE blocks as *.mod
>> files, which could then be re-read and re-parsed.
>>
>> Just two problems: To a) get the design right, and b) get the
>> implementation right.  This would take a lot of effort, and the
>> manpower simplfy isn't there (and it hasn't figured high on the
>> list of priorities).
>>
>> Of course, volunteers are always welcome.
> 
> The immediate interest is in whether it's possible to write translations
> of old .mods to newer formats to solve the existing issues, but that
> presumably only makes sense if you can reliably mix code compiled with
> old and new compiler versions.  I'll see how far I can get with module.c
> when I have a chance, thanks.
> 

It would be an order of magnitude easier and take less time if you just 
recompiled all of your sources.  I hope you use make or cmake or at 
least some build scripting and let it run overnight.  Or, does it take a 
week or two?

Regards,

Jerry

  reply	other threads:[~2018-03-14  2:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 15:40 Dave Love
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 [this message]
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=f4b02d10-0fa7-7fe1-0b13-3d0b0f14b036@charter.net \
    --to=jvdelisle@charter.net \
    --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).