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/104819] Reject NULL without MOLD as actual to an assumed-rank dummy
Date: Fri, 15 Mar 2024 21:08:23 +0000	[thread overview]
Message-ID: <bug-104819-4-rPULj7ekAO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104819-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 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:90442fb421823153c4f762a2d26a0d700af2e6c3

commit r13-8443-g90442fb421823153c4f762a2d26a0d700af2e6c3
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Fri Mar 1 19:21:27 2024 +0100

    Fortran: improve checks of NULL without MOLD as actual argument [PR104819]

    gcc/fortran/ChangeLog:

            PR fortran/104819
            * check.cc (gfc_check_null): Handle nested NULL()s.
            (is_c_interoperable): Check for MOLD argument of NULL() as part of
            the interoperability check.
            * interface.cc (gfc_compare_actual_formal): Extend checks for
NULL()
            actual arguments for presence of MOLD argument when required by
            Interp J3/22-146.

    gcc/testsuite/ChangeLog:

            PR fortran/104819
            * gfortran.dg/assumed_rank_9.f90: Adjust testcase use of NULL().
            * gfortran.dg/pr101329.f90: Adjust testcase to conform to interp.
            * gfortran.dg/null_actual_4.f90: New test.

    (cherry picked from commit db0b6746be075e43c8142585968483e125bb52d0)

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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 13:24 [Bug fortran/104819] New: " burnus at gcc dot gnu.org
2022-03-08  7:31 ` [Bug fortran/104819] " burnus at gcc dot gnu.org
2023-11-06 20:32 ` anlauf at gcc dot gnu.org
2023-11-06 20:46 ` anlauf at gcc dot gnu.org
2023-11-09 21:32 ` anlauf at gcc dot gnu.org
2023-11-12 21:02 ` anlauf at gcc dot gnu.org
2023-11-14 21:17 ` anlauf at gcc dot gnu.org
2023-11-16 20:19 ` anlauf at gcc dot gnu.org
2023-11-23 18:32 ` cvs-commit at gcc dot gnu.org
2024-02-29 21:01 ` anlauf at gcc dot gnu.org
2024-03-01 18:22 ` cvs-commit at gcc dot gnu.org
2024-03-15 21:08 ` cvs-commit at gcc dot gnu.org
2024-03-15 21:08 ` 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-104819-4-rPULj7ekAO@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).