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/95373] [9/10/11 Regression] ICE in build_reference_type, at tree.c:7942
Date: Wed, 27 May 2020 19:47:31 +0000 [thread overview]
Message-ID: <bug-95373-4-JV3AoopHTJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95373-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95373
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
Keywords|ice-on-valid-code |
CC| |kargl at gcc dot gnu.org
--- Comment #2 from kargl at gcc dot gnu.org ---
Removed keyword. It is an ICE-on-invalid with -std=f95;
code is valid for F2003 and newer.
Index: gcc/fortran/primary.c
===================================================================
--- gcc/fortran/primary.c (revision 280157)
+++ gcc/fortran/primary.c (working copy)
@@ -2242,7 +2242,12 @@ gfc_match_varspec (gfc_expr *primary, int equiv_flag,
sym = NULL;
if (sep == '%' && primary->ts.type != BT_UNKNOWN)
- intrinsic = true;
+ {
+ if (!gfc_notify_std (GFC_STD_F2003,
+ "Invalid type parameter inquiry at %C"))
+ return MATCH_ERROR;
+ intrinsic = true;
+ }
}
else
inquiry = false;
next prev parent reply other threads:[~2020-05-27 19:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 19:01 [Bug fortran/95373] New: " gscfq@t-online.de
2020-05-27 19:11 ` [Bug fortran/95373] " marxin at gcc dot gnu.org
2020-05-27 19:47 ` kargl at gcc dot gnu.org [this message]
2020-05-27 20:04 ` anlauf at gcc dot gnu.org
2020-05-27 20:30 ` sgk at troutmask dot apl.washington.edu
2020-05-28 7:37 ` rguenth at gcc dot gnu.org
2020-05-28 20:33 ` cvs-commit at gcc dot gnu.org
2020-05-28 20:39 ` anlauf at gcc dot gnu.org
2020-05-29 9:52 ` clyon at gcc dot gnu.org
2020-05-29 20:51 ` anlauf at gcc dot gnu.org
2020-05-30 19:00 ` cvs-commit at gcc dot gnu.org
2020-05-30 19:02 ` anlauf at gcc dot gnu.org
2020-06-05 21:03 ` cvs-commit at gcc dot gnu.org
2020-06-05 21:03 ` cvs-commit at gcc dot gnu.org
2020-06-05 21:17 ` cvs-commit at gcc dot gnu.org
2020-06-05 21:17 ` cvs-commit at gcc dot gnu.org
2020-06-05 21:18 ` 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-95373-4-JV3AoopHTJ@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).