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/112772] Some issues with OPTIONAL, ALLOCATABLE dummy arguments
Date: Fri, 01 Dec 2023 21:21:40 +0000	[thread overview]
Message-ID: <bug-112772-4-Beh32K5Kq0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112772-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:7317275497e10c4a0fb3fbaa6ca87f3463ac124d

commit r14-6066-g7317275497e10c4a0fb3fbaa6ca87f3463ac124d
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Thu Nov 30 21:53:21 2023 +0100

    Fortran: copy-out for possibly missing OPTIONAL CLASS arguments [PR112772]

    gcc/fortran/ChangeLog:

            PR fortran/112772
            * trans-expr.cc (gfc_conv_class_to_class): Make copy-out
conditional
            on the presence of an OPTIONAL CLASS argument passed to an OPTIONAL
            CLASS dummy.

    gcc/testsuite/ChangeLog:

            PR fortran/112772
            * gfortran.dg/missing_optional_dummy_7.f90: New test.

  parent reply	other threads:[~2023-12-01 21:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 21:35 [Bug fortran/112772] New: " anlauf at gcc dot gnu.org
2023-11-30 20:48 ` [Bug fortran/112772] " anlauf at gcc dot gnu.org
2023-11-30 21:08 ` anlauf at gcc dot gnu.org
2023-12-01 21:03 ` anlauf at gcc dot gnu.org
2023-12-01 21:21 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-02 14:23 ` 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-112772-4-Beh32K5Kq0@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).