public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41453] use INTENT(out) for optimization
Date: Sun, 25 Sep 2022 12:48:17 +0000	[thread overview]
Message-ID: <bug-41453-4-98HdHo19fx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-41453-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41453

--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Mikael Morin <mikael@gcc.gnu.org>:

https://gcc.gnu.org/g:51c9480f9f0a80ef112ba2aed040b0b2ad0fc2a2

commit r13-2837-g51c9480f9f0a80ef112ba2aed040b0b2ad0fc2a2
Author: Mikael Morin <mikael@gcc.gnu.org>
Date:   Mon Aug 29 13:27:02 2022 +0200

    fortran: Support clobbering of reference variables [PR41453]

    This adds support for clobbering of variables passed by reference,
    when the reference is forwarded to a subroutine as actual argument
    whose associated dummy has the INTENT(OUT) attribute.
    This was explicitly disabled by a condition added with
    r9-3032-gee7fb0588c6361b4d77337ab0f7527be64fcdde2 and removing that
    condition seems to work, as demonstrated by the new testcase.

            PR fortran/41453
            PR fortran/87395

    gcc/fortran/ChangeLog:

            * trans-expr.cc (gfc_conv_procedure_call): Remove condition
            disabling clobber generation for dummy variables.  Remove
            obsolete comment.

    gcc/testsuite/ChangeLog:

            * gfortran.dg/intent_optimize_6.f90: New test.

  parent reply	other threads:[~2022-09-25 12:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-41453-4@http.gcc.gnu.org/bugzilla/>
2012-06-29 14:26 ` [Bug middle-end/41453] " Joost.VandeVondele at mat dot ethz.ch
2013-03-29  9:04 ` Joost.VandeVondele at mat dot ethz.ch
2022-08-25 19:31 ` anlauf at gcc dot gnu.org
2022-08-25 19:58 ` [Bug fortran/41453] " anlauf at gcc dot gnu.org
2022-09-25 12:48 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-25 12:48 ` cvs-commit at gcc dot gnu.org
2022-09-25 12:48 ` cvs-commit at gcc dot gnu.org
2022-09-25 12:48 ` cvs-commit at gcc dot gnu.org
2022-09-25 12:48 ` cvs-commit at gcc dot gnu.org
2022-09-25 16:42 ` mikael at gcc dot gnu.org
2022-09-25 20:32 ` tkoenig at gcc dot gnu.org

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=bug-41453-4-98HdHo19fx@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).