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/114012] overloaded unary operator called twice
Date: Wed, 06 Mar 2024 21:03:50 +0000	[thread overview]
Message-ID: <bug-114012-4-G40LxTfo7F@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114012-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:

https://gcc.gnu.org/g:1f5787e4b803a4294eeb80e048f56ccdb99c1b3b

commit r13-8407-g1f5787e4b803a4294eeb80e048f56ccdb99c1b3b
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Sun Feb 25 21:18:23 2024 +0100

    Fortran: do not evaluate polymorphic functions twice in assignment
[PR114012]

            PR fortran/114012

    gcc/fortran/ChangeLog:

            * trans-expr.cc (gfc_conv_procedure_call): Evaluate non-trivial
            arguments just once before assigning to an unlimited polymorphic
            dummy variable.

    gcc/testsuite/ChangeLog:

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

    (cherry picked from commit 2f71e801ad0bb1f620334aadbd7c99cc4efe6309)

  parent reply	other threads:[~2024-03-06 21:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 14:14 [Bug fortran/114012] New: " alexandre.poux at coria dot fr
2024-02-20 20:32 ` [Bug fortran/114012] " anlauf at gcc dot gnu.org
2024-02-25 19:44 ` anlauf at gcc dot gnu.org
2024-02-25 20:36 ` anlauf at gcc dot gnu.org
2024-02-26 17:50 ` cvs-commit at gcc dot gnu.org
2024-02-27  9:42 ` alexandre.poux at coria dot fr
2024-03-06 21:03 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-06 21:06 ` anlauf 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-114012-4-G40LxTfo7F@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).