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/101334] New: gfortran fails to enforce C838 on disallowed uses of assumed-rank variable names + bogus errors
Date: Mon, 05 Jul 2021 18:57:39 +0000	[thread overview]
Message-ID: <bug-101334-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 101334
           Summary: gfortran fails to enforce C838 on disallowed uses of
                    assumed-rank variable names + bogus errors
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: sandra at gcc dot gnu.org
  Target Milestone: ---

C838 in the 2018 Fortran standard (originally C535b in TS29113) says:

An assumed-rank variable name shall not appear in a designator or expression
except as an actual argument that corresponds to a dummy argument that is
assumed-rank, the argument of the function C_LOC or C_SIZEOF from the intrinsic
module ISO_C_BINDING (18.2), the first dummy argument of an intrinsic inquiry
function, or the selector of a SELECT RANK statement.

The WIP TS29113 testsuite

https://gcc.gnu.org/pipermail/gcc-patches/2021-July/574115.html

has tests types/c535b-*.f90 for this.  c535b-2 and c535b-3 are failing with
several cases of missing diagnostics, or bogus errors.  E.g. the latter test
case focuses on the 2-argument form of the ASSOCIATED intrinsic and produces
errors like

Error: 'pointer' argument of 'associated' intrinsic at (1) must be of rank -1

in a context where I think assumed-rank should be allowed (first argument to an
intrinsic inquiry function).

             reply	other threads:[~2021-07-05 18:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 18:57 sandra at gcc dot gnu.org [this message]
2021-09-23  0:11 ` [Bug fortran/101334] " cvs-commit at gcc dot gnu.org
2021-09-26 17:26 ` cvs-commit at gcc dot gnu.org
2021-10-21 21:14 ` 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-101334-4@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).