public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <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 22:22:20 +0000 [thread overview]
Message-ID: <bug-105243-4-NisN9866BA@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
--- Comment #6 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Mon, May 16, 2022 at 10:16:51PM +0000, sgk at troutmask dot
apl.washington.edu wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105243
>
> --- Comment #5 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
> On Mon, May 16, 2022 at 08:27:24PM +0000, anlauf at gcc dot gnu.org wrote:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105243
> >
> > --- Comment #3 from anlauf at gcc dot gnu.org ---
> > (In reply to kargl from comment #2)
> > > This fixes the problem. Someone that regularly use git will need to commit
> > > it.
> >
> > Are you sure this is the right solution?
> >
>
> I quoted the F2018 standard constraint.
>
> C708 An entity declared with the CLASS keyword shall be a dummy
> argument or have the ALLOCATABLE or POINTER attribute.
>
> class(t), parameter :: y
>
> would seem to be missing all of the three listed attributes.
>
I'll also add
7.3.2.3 CLASS type specifier
The CLASS type specifier is used to declare polymorphic entities.
A polymorphic entity is a data entity that is able to be of differing
dynamic types during program execution.
Does is make sense to given a named constant the polymorphic property?
next prev parent reply other threads:[~2022-05-16 22:22 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
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 [this message]
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-NisN9866BA@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).