public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/102503] ICE in gfc_conv_array_bound, at fortran/trans-types.c:1224
Date: Fri, 22 Oct 2021 16:00:20 +0000	[thread overview]
Message-ID: <bug-102503-4-44ZLFl8Pze@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102503-4@http.gcc.gnu.org/bugzilla/>

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu.org

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
F2018:C837 An assumed-rank entity shall be a dummy data object that does not
have the CODIMENSION or VALUE attribute.

In principle, something like the following should do - but reading the file
shows that there are many more issues of the same kind :-(

--- a/gcc/fortran/resolve.c
+++ b/gcc/fortran/resolve.c
@@ -15623,7 +15623,7 @@ resolve_symbol (gfc_symbol *sym)
          return;
        }
       if (as->type == AS_ASSUMED_RANK
-         && (sym->attr.codimension || sym->attr.value))
+         && (class_attr->attr.codimension || sym->attr.value))
        {
          gfc_error ("Assumed-rank array at %L may not have the VALUE or "
                     "CODIMENSION attribute", &sym->declared_at);

      parent reply	other threads:[~2021-10-22 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 19:46 [Bug fortran/102503] New: " gscfq@t-online.de
2021-10-22 12:12 ` [Bug fortran/102503] " dominiq at lps dot ens.fr
2021-10-22 16:00 ` burnus 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-102503-4-44ZLFl8Pze@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).