From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Harald Anlauf <anlauf@gmx.de>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Subject: Re: PING [PATCH] PR fortran/99839 - [9/10/11/12 Regression] ICE in inline_matmul_assign, at fortran/frontend-passes.c:4234
Date: Fri, 4 Jun 2021 16:46:45 +0100 [thread overview]
Message-ID: <CAGkQGiJPQtMWo9BFYesw+rWHWUWEpaLsAAqs5A_jhniXUMAGOg@mail.gmail.com> (raw)
In-Reply-To: <trinity-4f4523e7-d5fd-4696-81d3-f7cf24f9081f-1622751680170@3c-app-gmx-bs43>
Hi Harald,
Looks good to me - OK for as many branches as you have sufficient fortitude
for.
Regards
Paul
On Thu, 3 Jun 2021 at 21:22, Harald Anlauf via Fortran <fortran@gcc.gnu.org>
wrote:
> *PING*
>
> > Gesendet: Donnerstag, 27. Mai 2021 um 22:20 Uhr
> > Von: "Harald Anlauf" <anlauf@gmx.de>
> > An: "fortran" <fortran@gcc.gnu.org>, "gcc-patches" <
> gcc-patches@gcc.gnu.org>
> > Betreff: [PATCH] PR fortran/99839 - [9/10/11/12 Regression] ICE in
> inline_matmul_assign, at fortran/frontend-passes.c:4234
> >
> > Dear Fortranners,
> >
> > frontend optimization tries to inline matmul, but then it also needs
> > to take care of the assignment to the result array. If that one is
> > not of canonical type, we currently get an ICE. The straightforward
> > solution is to simply punt in those cases and avoid inlining.
> >
> > Regtested on x86_64-pc-linux-gnu.
> >
> > OK for mainline? Backport to affected branches?
> >
> > Thanks,
> > Harald
> >
> >
> > Fortran - ICE in inline_matmul_assign
> >
> > Restrict inlining of matmul to those cases where assignment to the
> > result array does not need special treatment.
> >
> > gcc/fortran/ChangeLog:
> >
> > PR fortran/99839
> > * frontend-passes.c (inline_matmul_assign): Do not inline matmul
> > if the assignment to the resulting array if it is not of canonical
> > type (real/integer/complex/logical).
> >
> > gcc/testsuite/ChangeLog:
> >
> > PR fortran/99839
> > * gfortran.dg/inline_matmul_25.f90: New test.
> >
> >
>
--
"If you can't explain it simply, you don't understand it well enough" -
Albert Einstein
prev parent reply other threads:[~2021-06-04 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 20:20 Harald Anlauf
2021-06-03 20:21 ` PING " Harald Anlauf
2021-06-04 15:46 ` Paul Richard Thomas [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=CAGkQGiJPQtMWo9BFYesw+rWHWUWEpaLsAAqs5A_jhniXUMAGOg@mail.gmail.com \
--to=paul.richard.thomas@gmail.com \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).