This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Loop fusion.

On 04/23/2018 01:00 PM, Richard Biener wrote:

On Sun, Apr 22, 2018 at 4:27 PM, Toon Moene <> wrote:
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:


The reaction from one of the members of the committee (about "their"

'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 ?

In principle GRAPHITE can handle loop fusion but yes, standalone fusion
is sth useful.

Note that while it looks "obvious" in the above source fragment the IL
that is presented to optimizers may make things a lot less "low-hanging".

Well, the loops are generated by the front end, so I *assume* they are basically the same ...

Probably the largest problem to address is the heuristic for preventing register pressure going through the roof ...

Toon Moene - e-mail: - phone: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
At home:; weather:
Progress of GNU Fortran:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]