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: Thu, 23 Nov 2023 18:32:55 +0000 [thread overview] Message-ID: <bug-104819-4-GVoWcXnUjp@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 #8 from CVS 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:7646b5d88056cf269ff555afe95bc361dcf5e5c0 commit r14-5798-g7646b5d88056cf269ff555afe95bc361dcf5e5c0 Author: Harald Anlauf <anlauf@gmx.de> Date: Wed Nov 22 21:45:46 2023 +0100 testsuite: fortran: fix invalid testcases (missing MOLD argument to NULL) The Fortran standard requires that NULL() passed to an assumed-rank dummy argument has a MOLD argument. gcc/testsuite/ChangeLog: PR fortran/104819 * gfortran.dg/assumed_rank_10.f90: Add MOLD argument to NULL(). * gfortran.dg/assumed_rank_8.f90: Likewise.
next prev parent reply other threads:[~2023-11-23 18:32 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 [this message] 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
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-GVoWcXnUjp@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).