From: Tobias Burnus <burnus@net-b.de>
To: "Thomas König" <tk@tkoenig.net>,
"Janne Blomqvist" <blomqvist.janne@gmail.com>,
"Thomas Koenig" <tkoenig@netcologne.de>
Cc: Tobias Burnus <tobias@codesourcery.com>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran] Load scalar intent-in variables at the beginning of procedures
Date: Wed, 20 Nov 2019 22:30:00 -0000 [thread overview]
Message-ID: <94da433a-f9e3-8fb7-ea59-c1f798e4e0fb@net-b.de> (raw)
In-Reply-To: <4e68f250-1e41-ac7c-dc64-88f91cdf183e@tkoenig.net>
On 11/20/19 10:35 PM, Thomas König wrote:
> I haven't run any actual benchmarks.
I think it would be interesting – I think there can be quite some
advantages in some cases, while in most cases, it is not really noticable.
> Of course, Fortran language rules specify that the call to bar cannot
> do anything to n, but apparently we do not tell the gcc middle end
> that this is the case, or maybe that there is no way to really specify
> this.
To my knowledge, the ME does not support the Fortran semantics but
assumes that once a pointer escapes in one procedure call, any other
procedure might have access to it and modify it as well. This matches
(effectively) the Fortran semantics of asynchronous. See also PR 49733.
The only thing we can do currently is to specify the intent via 'fn
spec' which helps a bit – but not if the pointer has already escaped.
Maybe we should think again about handling this properly in the ME.
Cheers,
Tobias
next prev parent reply other threads:[~2019-11-20 22:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 21:57 Thomas König
2019-11-11 22:08 ` Thomas Koenig
2019-11-11 22:53 ` Janne Blomqvist
2019-11-11 23:02 ` Thomas König
2019-11-12 7:48 ` Janne Blomqvist
2019-11-12 12:50 ` Thomas König
2019-11-12 14:33 ` Tobias Burnus
2019-11-12 17:22 ` Thomas König
2019-11-15 7:41 ` Tobias Burnus
2019-11-15 18:07 ` Thomas König
2019-11-16 20:42 ` Thomas Koenig
2019-11-19 10:46 ` Bernhard Reutner-Fischer
2019-11-19 23:04 ` Thomas Koenig
2019-11-20 18:00 ` Bernhard Reutner-Fischer
2019-11-20 20:45 ` Janne Blomqvist
2019-11-20 21:07 ` Steve Kargl
2019-11-20 21:35 ` Bernhard Reutner-Fischer
2019-11-20 20:46 ` Janne Blomqvist
2019-11-20 21:39 ` Thomas König
2019-11-20 22:19 ` Janne Blomqvist
2019-11-20 22:32 ` Janne Blomqvist
2019-11-21 9:35 ` Janne Blomqvist
2019-11-20 22:37 ` Tobias Burnus
2019-11-20 22:41 ` Thomas König
2019-11-20 22:30 ` Tobias Burnus [this message]
2019-11-21 9:41 ` Tobias Burnus
2019-11-21 12:30 ` Richard Biener
2019-11-21 13:17 ` Tobias Burnus
2019-11-21 13:37 ` Tobias Burnus
2019-11-21 14:10 ` Richard Biener
2019-11-21 14:39 ` Tobias Burnus
2019-11-22 10:44 ` Tobias Burnus
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=94da433a-f9e3-8fb7-ea59-c1f798e4e0fb@net-b.de \
--to=burnus@net-b.de \
--cc=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tk@tkoenig.net \
--cc=tkoenig@netcologne.de \
--cc=tobias@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).