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/110618] Dependency between arguments when one is allocatable array whose dummy is intent(out)
Date: Mon, 17 Jul 2023 12:16:43 +0000	[thread overview]
Message-ID: <bug-110618-4-QZ2vS9rqrE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110618-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 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:1a46400e5ac0f21eead74b10752f69ebc7a8be27

commit r14-2579-g1a46400e5ac0f21eead74b10752f69ebc7a8be27
Author: Mikael Morin <mikael@gcc.gnu.org>
Date:   Mon Jul 17 14:14:18 2023 +0200

    fortran: Use pre-evaluated class container if available [PR110618]

    Add the possibility to provide a pre-evaluated class container argument
    to gfc_add_finalizer to avoid repeatedly evaluating data reference
    expressions in the generated code.

            PR fortran/110618

    gcc/fortran/ChangeLog:

            * trans.h (gfc_add_finalizer_call): Add class container argument.
            * trans.cc (gfc_add_finalizer_call): Ditto.  Pass down new
            argument to get_final_proc_ref, get_elem_size, get_var_desc,
            and get_vptr.
            (get_elem_size): Add class container argument.
            Use provided class container if it's available.
            (get_var_descr): Same.
            (get_vptr): Same.
            (get_final_proc_ref): Same.  Add boolean telling the class
            container argument is used.  Set it.  Don't try to use
            final_wrapper if class container argument was used.

  parent reply	other threads:[~2023-07-17 12:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 18:26 [Bug fortran/110618] New: " mikael at gcc dot gnu.org
2023-07-10 20:53 ` [Bug fortran/110618] " mikael at gcc dot gnu.org
2023-07-13 19:29 ` mikael at gcc dot gnu.org
2023-07-17 12:16 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-17 12:16 ` cvs-commit at gcc dot gnu.org
2023-07-17 17:46 ` mikael 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-110618-4-QZ2vS9rqrE@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).