public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Koenig <tkoenig@netcologne.de>
To: "Mikael Morin" <morin-mikael@orange.fr>,
	"Théo Cavignac" <theo.cavignac@gmail.com>
Cc: gfortran <fortran@gcc.gnu.org>
Subject: Re: Optimization of spread
Date: Thu, 3 Nov 2022 23:04:12 +0100	[thread overview]
Message-ID: <88d8e0b3-8c75-2ccc-79bc-e9b621f0794c@netcologne.de> (raw)
In-Reply-To: <8f4bdd1c-44f1-fb2f-fdc2-f7fcbef17c43@orange.fr>

Hi,

Mikael beat me to a mail saying essentially the same things by
a few minutes, so I'm just adding a few details.

> There are two places where inlining can be done:
>   * In front-end passes where the parsed fortran code is rewritten 
> before generating the intermediary code for the optimizers.  Thomas 
> König can help you there.

I most certainly can.  frontend-passes.cc contains, among other
functionality, a function to inline MATMUL for small sizes, so
much of the infrastructure is already there.

>   * Directly in the code generation for the optimizers.  It is (much) 
> more complex but can avoid the need for temporaries.  I can help you there.
> 
> Some links about our development process and conventions:
> https://gcc.gnu.org/contribute.html
> https://gcc.gnu.org/git.html

And, if you're into hacking gfortran, some starting pointers are at
https://gcc.gnu.org/wiki/GFortranHacking . But always free feel to ask!

Best regards

	Thomas

  reply	other threads:[~2022-11-03 22:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 10:48 Théo Cavignac
2022-11-03 21:54 ` Mikael Morin
2022-11-03 22:04   ` Thomas Koenig [this message]
2022-11-16 10:12     ` Théo Cavignac

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=88d8e0b3-8c75-2ccc-79bc-e9b621f0794c@netcologne.de \
    --to=tkoenig@netcologne.de \
    --cc=fortran@gcc.gnu.org \
    --cc=morin-mikael@orange.fr \
    --cc=theo.cavignac@gmail.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).