public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/105243] ICE in next_char, at fortran/io.cc:160
Date: Mon, 16 May 2022 00:06:14 +0000	[thread overview]
Message-ID: <bug-105243-4-I14JeH32vv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105243-4@http.gcc.gnu.org/bugzilla/>

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

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2022-05-16
           Priority|P3                          |P4
                 CC|                            |kargl at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #2 from kargl at gcc dot gnu.org ---
This fixes the problem.  Someone that regularly use git will need to commit it.

diff --git a/gcc/fortran/decl.cc b/gcc/fortran/decl.cc
index bd586e75008..6712efd6ec8 100644
--- a/gcc/fortran/decl.cc
+++ b/gcc/fortran/decl.cc
@@ -6283,6 +6283,15 @@ gfc_match_data_decl (void)
       goto cleanup;
     }

+  /* F2018:C708.  */
+  if (current_ts.type == BT_CLASS && current_attr.flavor == FL_PARAMETER)
+    {
+      gfc_error ("CLASS entity at %C shall be a dummy argument or have the "
+                "ALLOCATABLE or POINTER attribute.");
+      m = MATCH_ERROR;
+      goto cleanup;
+    }
+
 ok:
   /* If we have an old-style character declaration, and no new-style
      attribute specifications, then there a comma is optional between

  parent reply	other threads:[~2022-05-16  0:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 17:21 [Bug fortran/105243] New: " gscfq@t-online.de
2022-04-12 17:22 ` [Bug fortran/105243] " gscfq@t-online.de
2022-05-16  0:06 ` kargl at gcc dot gnu.org [this message]
2022-05-16 20:27 ` anlauf at gcc dot gnu.org
2022-05-16 21:06 ` anlauf at gcc dot gnu.org
2022-05-16 22:16 ` sgk at troutmask dot apl.washington.edu
2022-05-16 22:22 ` sgk at troutmask dot apl.washington.edu
2022-05-17 19:56 ` anlauf at gcc dot gnu.org
2022-05-17 23:21 ` sgk at troutmask dot apl.washington.edu
2022-06-29 19:42 ` anlauf at gcc dot gnu.org
2022-06-29 19:54 ` anlauf at gcc dot gnu.org
2022-06-29 20:27 ` sgk at troutmask dot apl.washington.edu
2022-06-30 19:01 ` cvs-commit at gcc dot gnu.org
2022-07-03 19:44 ` cvs-commit at gcc dot gnu.org
2022-07-03 20:13 ` cvs-commit at gcc dot gnu.org
2022-07-03 20:29 ` cvs-commit at gcc dot gnu.org
2022-07-03 20:33 ` anlauf 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-105243-4-I14JeH32vv@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).