public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/54753] assumed-rank dummies: Reject assumed-size actuals in in some cases (C535c; in F2018: C839)
Date: Thu, 07 Oct 2021 15:17:03 +0000	[thread overview]
Message-ID: <bug-54753-4-RmAJ9lKC6J@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54753-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from sandra at gcc dot gnu.org ---
Patch to add the diagnostic posted here:

https://gcc.gnu.org/pipermail/fortran/2021-October/056656.html

There's still a problem with the bogus diagnostic arising from
deallocation/initialization when you have just a subroutine definition instead
of an interface.  That has nothing to do with this diagnostic or other
caller/callee argument mismatch so I opened a new issue (PR102641) for that.

  parent reply	other threads:[~2021-10-07 15:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-29 16:10 [Bug fortran/54753] New: assumed-rank dummies: Reject assumed-size actuals in in some cases (C535c) burnus at gcc dot gnu.org
2015-10-09 14:06 ` [Bug fortran/54753] " dominiq at lps dot ens.fr
2021-03-01  8:04 ` [Bug fortran/54753] assumed-rank dummies: Reject assumed-size actuals in in some cases (C535c; in F2018: C839) burnus at gcc dot gnu.org
2021-07-05 22:18 ` sandra at gcc dot gnu.org
2021-10-04  7:38 ` cvs-commit at gcc dot gnu.org
2021-10-07 15:17 ` sandra at gcc dot gnu.org [this message]
2021-10-08 21:31 ` cvs-commit at gcc dot gnu.org
2021-10-21 21:13 ` sandra 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-54753-4-RmAJ9lKC6J@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).