From: Janne Blomqvist <blomqvist.janne@gmail.com>
To: "Thomas König" <tk@tkoenig.net>
Cc: "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: Mon, 11 Nov 2019 22:53:00 -0000 [thread overview]
Message-ID: <CAO9iq9FNdOELT3hcoiLORgxF1C67HYC+HFQ+F0O5zDwG7udERA@mail.gmail.com> (raw)
In-Reply-To: <48286910-ebbb-10e4-488b-8c96e505375c@tkoenig.net>
On Mon, Nov 11, 2019 at 11:56 PM Thomas König <tk@tkoenig.net> wrote:
>
> Hello world,
>
> the attached patch loads scalar INTENT(IN) variables to a local
> variable at the start of a procedure, as suggested in PR 67202, in
> order to aid optimization. This is controlled by front-end
> optimization so it is easier to catch if any bugs should turn up :-)
>
> This is done to make optimization by the middle-end easier.
>
> I left in the parts for debugging that I added for this patch.
> Seeing the difference between EXEC_INIT_ASSIGN and EXEC_ASSIGN was
> particularly instructive.
>
> Regression-tested. OK for trunk?
Wouldn't it be even better to pass scalar intent(in) variables by
value? The obvious objection of course is ABI, but for procedures with
an explicit interface we're not following any particular ABI anyways?
--
Janne Blomqvist
next prev parent reply other threads:[~2019-11-11 22:42 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 [this message]
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
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=CAO9iq9FNdOELT3hcoiLORgxF1C67HYC+HFQ+F0O5zDwG7udERA@mail.gmail.com \
--to=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tk@tkoenig.net \
/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).