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/113377] Wrong code passing optional dummy argument to elemental procedure with optional dummy Date: Sun, 28 Jan 2024 19:26:37 +0000 [thread overview] Message-ID: <bug-113377-4-rQpbrgMu0t@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113377-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113377 --- Comment #12 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:c4773944bb3bec712b4002a2e599409301e50b11 commit r14-8479-gc4773944bb3bec712b4002a2e599409301e50b11 Author: Harald Anlauf <anlauf@gmx.de> Date: Thu Jan 25 22:19:10 2024 +0100 Fortran: NULL actual to optional dummy with VALUE attribute [PR113377] gcc/fortran/ChangeLog: PR fortran/113377 * trans-expr.cc (conv_dummy_value): Treat NULL actual argument to optional dummy with the VALUE attribute as not present. (gfc_conv_procedure_call): Likewise. gcc/testsuite/ChangeLog: PR fortran/113377 * gfortran.dg/optional_absent_11.f90: New test.
prev parent reply other threads:[~2024-01-28 19:26 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-13 14:21 [Bug fortran/113377] New: " anlauf at gcc dot gnu.org 2024-01-14 10:51 ` [Bug fortran/113377] " mikael at gcc dot gnu.org 2024-01-14 20:05 ` anlauf at gcc dot gnu.org 2024-01-16 21:05 ` anlauf at gcc dot gnu.org 2024-01-16 22:02 ` anlauf at gcc dot gnu.org 2024-01-19 18:46 ` mikael at gcc dot gnu.org 2024-01-19 19:25 ` mikael at gcc dot gnu.org 2024-01-19 21:16 ` anlauf at gcc dot gnu.org 2024-01-19 21:19 ` anlauf at gcc dot gnu.org 2024-01-21 20:24 ` cvs-commit at gcc dot gnu.org 2024-01-24 19:28 ` cvs-commit at gcc dot gnu.org 2024-01-25 18:26 ` anlauf at gcc dot gnu.org 2024-01-28 19:26 ` cvs-commit at gcc dot gnu.org [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=bug-113377-4-rQpbrgMu0t@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: linkBe 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).