From: Andre Vehreschild <vehre@gmx.de>
To: Bernhard Reutner-Fischer via Fortran <fortran@gcc.gnu.org>
Cc: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
Richard Biener <rguenther@suse.de>, Jan Hubicka <hubicka@ucw.cz>,
Tobias Burnus <burnus@net-b.de>,
gcc-patches@gcc.gnu.org
Subject: Re: New modref/ipa_modref optimization passes
Date: Fri, 23 Oct 2020 12:05:09 +0200 [thread overview]
Message-ID: <20201023120509.7c8f8070@vepi2> (raw)
In-Reply-To: <A3B7CCB5-110D-4FB2-9BC1-EFFF1BAA9E83@gmail.com>
On Fri, 23 Oct 2020 11:54:08 +0200
Bernhard Reutner-Fischer via Fortran <fortran@gcc.gnu.org> wrote:
> On 16 October 2020 11:20:23 CEST, Richard Biener <rguenther@suse.de> wrote:
>
> >IMHO the cleanest way would be to swap the CAF token field and
> >the dim[] field (which is an ABI change for -fcoarray)
>
> I think coarrays are new anyway so I suppose an ABI break is fine?
Coarrays are in the standard since Fortran 2008. So what I'd rather not call
them new being there for more than 10 years...
The descriptor is used in the opencoarrays library, too. And has to be kept in
sync. So when the ABI break is reasonable it's fine.
--
Andre Vehreschild * Email: vehre ad gmx dot de
prev parent reply other threads:[~2020-10-23 10:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <157394261677.27454.2367573047582814412@a285.localdomain>
[not found] ` <20200919223255.GA69342@kam.mff.cuni.cz>
[not found] ` <20200920061551.GA29500@kam.mff.cuni.cz>
2020-09-21 7:13 ` Richard Biener
2020-09-21 7:47 ` Jan Hubicka
2020-09-21 7:55 ` Richard Biener
2020-09-21 8:04 ` Jan Hubicka
2020-09-21 8:10 ` Richard Biener
2020-09-22 10:15 ` Tobias Burnus
2020-09-27 21:37 ` Jan Hubicka
2020-10-16 7:56 ` Jan Hubicka
2020-10-16 8:05 ` Richard Biener
2020-10-16 9:20 ` Richard Biener
2020-10-16 10:42 ` Richard Biener
2020-10-23 9:54 ` Bernhard Reutner-Fischer
2020-10-23 10:05 ` Andre Vehreschild [this message]
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=20201023120509.7c8f8070@vepi2 \
--to=vehre@gmx.de \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=rep.dot.nop@gmail.com \
--cc=rguenther@suse.de \
/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).