From: Jakub Jelinek <jakub@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org,
Tobias Burnus <burnus@net-b.de>
Subject: Re: [PR72741] Encode OpenACC 'routine' directive inside Fortran module files
Date: Thu, 28 Feb 2019 21:17:00 -0000 [thread overview]
Message-ID: <20190228211701.GG7611@tucnak> (raw)
In-Reply-To: <87y35zmxcv.fsf@euler.schwinge.homeip.net>
On Thu, Feb 28, 2019 at 10:12:00PM +0100, Thomas Schwinge wrote:
> On Wed, 15 Jun 2016 20:12:15 -0700, Cesar Philippidis <cesar@codesourcery.com> wrote:
> The code changes now are actually very simple. The "problem" is that
> we're incrementing the Fortran module version, 'MOD_VERSION', which
> breaks binary compatibility with Fortran module files created with
> earlier versions of GCC, which is something that is to be avoided, as
> I've heard. Or, is it not that bad actually?
It is bad and we certainly shouldn't change it on release branches.
There are many ways to deal with it without bumping MOD_VERSION in a
backwards but not forwards compatible way, so that a newer compiler will be
able to parse old *.mod files, and newer compiler new ones as long as this
problematic stuff doesn't appear in.
Jakub
next prev parent reply other threads:[~2019-02-28 21:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 3:12 [PATCH,openacc] check for compatible loop parallelism with acc routine calls Cesar Philippidis
2016-06-17 14:42 ` Jakub Jelinek
2016-06-23 16:05 ` Cesar Philippidis
2016-06-29 14:11 ` Thomas Schwinge
2016-06-29 14:35 ` Jakub Jelinek
2016-06-29 15:31 ` Cesar Philippidis
2019-02-28 21:12 ` [PR72741] Encode OpenACC 'routine' directive inside Fortran module files Thomas Schwinge
2019-02-28 21:17 ` Jakub Jelinek [this message]
2019-03-13 17:50 ` [PR72741] Encode OpenACC 'routine' directive's level of parallelism " Thomas Schwinge
2019-03-13 22:13 ` Thomas Koenig
2019-03-14 7:38 ` Thomas Schwinge
2019-03-20 10:09 ` Thomas Schwinge
2019-03-21 20:49 ` Thomas Koenig
2019-03-21 19:47 ` Thomas Schwinge
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=20190228211701.GG7611@tucnak \
--to=jakub@redhat.com \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=thomas@codesourcery.com \
/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).