From: Toon Moene <toon@moene.org>
To: gcc mailing list <gcc@gcc.gnu.org>
Subject: Loop fusion.
Date: Sun, 22 Apr 2018 15:23:00 -0000 [thread overview]
Message-ID: <71dd38d0-2dbc-0100-7419-6f1ca1d5e077@moene.org> (raw)
A few days ago there was a rant on the Fortran Standardization
Committee's e-mail list about Fortran's "whole array arithmetic" being
unoptimizable.
An example picked at random from our weather forecasting code:
ZQICE(1:NPROMA,1:NFLEVG) = PGFL(1:NPROMA,1:NFLEVG,YI%MP)
ZQLI(1:NPROMA,1:NFLEVG) = PGFL(1:NPROMA,1:NFLEVG,YL%MP)
ZQRAIN(1:NPROMA,1:NFLEVG) = PGFL(1:NPROMA,1:NFLEVG,YR%MP)
ZQSNOW(1:NPROMA,1:NFLEVG) = PGFL(1:NPROMA,1:NFLEVG,YS%MP)
The reaction from one of the members of the committee (about "their"
compiler):
'And multiple consecutive array statements with the same shape are
âfusedâ exactly so that the compiler can generate good cache use. This
sort of optimization is pretty low hanging fruit.'
As far as I can see loop fusion as a stand-alone optimization is not
supported as yet, although some mention is made in the context of graphite.
Is this something that should be pursued ?
Kind regards,
--
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
At home: http://moene.org/~toon/; weather: http://moene.org/~hirlam/
Progress of GNU Fortran: http://gcc.gnu.org/wiki/GFortran#news
next reply other threads:[~2018-04-22 14:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-22 15:23 Toon Moene [this message]
2018-04-23 11:00 ` Bin.Cheng
2018-04-23 12:31 ` Richard Biener
2018-04-23 12:47 ` Janne Blomqvist
2018-04-23 14:11 ` Richard Biener
2018-04-23 11:02 ` Richard Biener
2018-04-24 2:22 ` Toon Moene
2018-04-24 12:58 ` Richard Biener
2018-04-25 8:06 ` Toon Moene
-- strict thread matches above, loose matches on Subject: below --
2015-04-22 19:19 Toon Moene
2015-04-22 20:05 ` Steven Bosscher
2015-04-23 4:58 ` Toon Moene
2015-04-23 17:17 ` Richard Biener
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=71dd38d0-2dbc-0100-7419-6f1ca1d5e077@moene.org \
--to=toon@moene.org \
--cc=gcc@gcc.gnu.org \
/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).