From: Tobias Burnus <tobias@codesourcery.com>
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: Thu, 21 Nov 2019 09:41:00 -0000 [thread overview]
Message-ID: <4ecba99c-f63a-628c-0778-d651503f7aa6@codesourcery.com> (raw)
In-Reply-To: <4e68f250-1e41-ac7c-dc64-88f91cdf183e@tkoenig.net>
On 11/20/19 10:35 PM, Thomas König wrote:
>> Is there a risk of performance regressions due to higher register
>> pressure?
richi points out (on IRC) that ideally LTO IPA opts would promote the
call-by reference to call-by value – but is not sure that it indeed
happens. [In any case, Linux distros have started to compile packages
with LTO.]
One could try and see whether that indeed happens. – Still, I think the
real solution is to teach the middle end about the Fortran semantics.
Cheers,
Tobia
next prev parent reply other threads:[~2019-11-21 9:35 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
2019-11-21 9:41 ` Tobias Burnus [this message]
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=4ecba99c-f63a-628c-0778-d651503f7aa6@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tk@tkoenig.net \
--cc=tkoenig@netcologne.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).