public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Harald Anlauf <anlauf@gmx.de>
To: gcc-patches@gcc.gnu.org
Cc: fortran@gcc.gnu.org
Subject: Re: [PATCH 0/2] fortran: Ignore unused arguments for scalarisation [PR97896]
Date: Sun, 7 Nov 2021 22:45:30 +0100	[thread overview]
Message-ID: <e62c2497-7707-6fe3-b1e7-b7b454d7d0d8@gmx.de> (raw)
Message-ID: <20211107214530.PQ4MPFxnE4BwKq8OCrC159ObVqWPurCpBLsP8NbHMag@z> (raw)
In-Reply-To: <20211107161746.1167205-1-mikael@gcc.gnu.org>

Hi Mikael,

thanks for working on this!

Am 07.11.21 um 17:17 schrieb Mikael Morin via Gcc-patches:
> Hello,
> 
> I repost this patch series initially targetted at the 11 branch only [1],
> and that I now would like to commit to master as well before.
> 
> The problematic case is intrinsic procedures where an argument is actually
> not used in the code generated (KIND argument of INDEX in the testcase),
> which confuses the scalariser.
> 
> Thomas König comitted a change to workaround the problem, but it regressed
> in PR97896.  These patch put the workaround where I think it is more
> appropriate, namely at the beginning of the scalarisation procedure.
> This is the patch 2 of the series, preceded with the revert in patch 1.
> I intend to commit both of them squashed together.
> 
> Regression-tested on x86_64-linux-gnu.  Ok for master and 11 branch?
> 
> 
> Changes from v1:
> 
>    Rebase on master.
> 
> 
> [1] https://gcc.gnu.org/pipermail/fortran/2021-August/056329.html
> 
> 
> Mikael Morin (2):
>    Revert "Remove KIND argument from INDEX so it does not mess up
>      scalarization."
>    fortran: Ignore unused args in scalarization [PR97896]
> 
>   gcc/fortran/intrinsic.c               | 48 +++------------------
>   gcc/fortran/intrinsic.h               |  3 +-
>   gcc/fortran/iresolve.c                | 21 ++-------
>   gcc/fortran/trans-array.c             | 61 ++++++++++++++++++++++++++-
>   gcc/fortran/trans-array.h             |  3 ++
>   gcc/fortran/trans-decl.c              | 24 +----------
>   gcc/fortran/trans-intrinsic.c         |  1 +
>   gcc/fortran/trans-stmt.c              | 20 +++++++++
>   gcc/testsuite/gfortran.dg/index_5.f90 | 23 ++++++++++
>   9 files changed, 121 insertions(+), 83 deletions(-)
>   create mode 100644 gcc/testsuite/gfortran.dg/index_5.f90
> 

LGTM at first sight.  But you may want to wait for Tobias or Thomas to
take a second look.

Thanks for the patch!

Harald


  parent reply	other threads:[~2021-11-07 21:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-07 16:17 Mikael Morin
2021-11-07 16:17 ` [PATCH 1/2] Revert "Remove KIND argument from INDEX so it does not mess up scalarization." Mikael Morin
2021-11-07 16:17 ` [PATCH 2/2] fortran: Ignore unused args in scalarization [PR97896] Mikael Morin
2021-11-07 21:45 ` Harald Anlauf [this message]
2021-11-07 21:45   ` [PATCH 0/2] fortran: Ignore unused arguments for scalarisation [PR97896] Harald Anlauf
2021-11-11 18:34 ` Thomas Koenig
2021-11-12 12:17 ` [committed] " Mikael Morin
  -- strict thread matches above, loose matches on Subject: below --
2021-08-07 18:32 [PATCH 0/2] " Mikael Morin

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=e62c2497-7707-6fe3-b1e7-b7b454d7d0d8@gmx.de \
    --to=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).