From: "Théo Cavignac" <theo.cavignac@gmail.com>
To: gfortran <fortran@gcc.gnu.org>
Subject: Re: Optimization of spread
Date: Wed, 16 Nov 2022 11:12:11 +0100 [thread overview]
Message-ID: <CALzWbOy9eKOp=wqLjtXOnEHZ0BX3k4Wa8mn74NdzxfYfo2Goxg@mail.gmail.com> (raw)
In-Reply-To: <88d8e0b3-8c75-2ccc-79bc-e9b621f0794c@netcologne.de>
Mikael, Thomas,
Thank you very much for being so welcoming.
> The source is actually more C than C++ (the fortran front-end at least).
That's good to know, I am much more comfortable with C.
> It requires little C++ skills, but time and willingness to decipher its complexity.
Yes, I don't expect that to be easy.
> 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.
> * 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.
My understanding of the compiler inner working being what it is, I
will try to have a look at the higher level side first.
> 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.
I will start my investigation 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!
I am familiar with git, but I'll have to read the two other documents soon.
Thanks again, hopefully you'll ear about me a little later.
Best regards,
Théo
On Thu, Nov 3, 2022 at 11:04 PM Thomas Koenig <tkoenig@netcologne.de> wrote:
>
> 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
prev parent reply other threads:[~2022-11-16 10:12 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
2022-11-16 10:12 ` Théo Cavignac [this message]
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='CALzWbOy9eKOp=wqLjtXOnEHZ0BX3k4Wa8mn74NdzxfYfo2Goxg@mail.gmail.com' \
--to=theo.cavignac@gmail.com \
--cc=fortran@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).