public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: Harald Anlauf <anlauf@gmx.de>, fortran <fortran@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR fortran/99169 - [9/10/11 Regression] Segfault when passing allocatable scalar into intent(out) dummy argument
Date: Sat, 20 Feb 2021 22:02:59 +0100	[thread overview]
Message-ID: <66a6553d-0c50-be78-fe2d-94c9cf912b42@codesourcery.com> (raw)
In-Reply-To: <trinity-1d5f2707-39e5-491b-88a8-2a9067b9557d-1613769381805@3c-app-gmx-bs31>

Dear Harald,

On 19.02.21 22:16, Harald Anlauf via Fortran wrote:
> we should not clobber the pointer in case of an allocatable scalar being
> an intent(out) dummy argument to a procedure.
>
> Regtested on x86_64-pc-linux-gnu.
> OK for master?  Since this is a regression, also for backports to 10/9?

OK to both master and to backporting.

Thanks for the patch!

Tobias

> PR fortran/99169 - Do not clobber allocatable intent(out) dummy argument
>
> gcc/fortran/ChangeLog:
>
>       * trans-expr.c (gfc_conv_procedure_call): Do not add clobber to
>       allocatable intent(out) argument.
>
> gcc/testsuite/ChangeLog:
>
>       * gfortran.dg/intent_optimize_3.f90: New test.
>
-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstrasse 201, 80634 München Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Frank Thürauf

      reply	other threads:[~2021-02-20 21:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 21:16 Harald Anlauf
2021-02-20 21:02 ` Tobias Burnus [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=66a6553d-0c50-be78-fe2d-94c9cf912b42@codesourcery.com \
    --to=tobias@codesourcery.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).