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/102331] ICE in attr_decl1, at fortran/decl.c:8691
Date: Wed, 15 Sep 2021 21:59:54 +0000	[thread overview]
Message-ID: <bug-102331-4-xZmxI76Mdr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102331-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Wed, Sep 15, 2021 at 08:57:45PM +0000, anlauf at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102331
> 
> --- Comment #3 from anlauf at gcc dot gnu.org ---
> (In reply to kargl from comment #2)
> > The following patch fixes the problem.  It has not been regression tested.
> 
> This restores the error, but for CLASS I now get:
> 
> pr102331.f90:2:3:
> 
>     2 |   allocatable :: f
>       |   1
> Error: Unclassifiable statement at (1)
> pr102331.f90:1:0:
> 
>     1 | class(t) function f()
>       | 
> Error: The type for function 'f' at (1) is not accessible
> 
> while the error message for line 2 does not show up for TYPE.
> Maybe there are a few more places that need fixing.
> (Not only the obvious one after the second hunk for parse.c).
> 

Yes, likely, 'ts.type == BT_CLASS' needs to be sprinkled in
other places.  Unfortunately, the 'Unclassifiable statement' 
error is a last resort catch-all error.  I know little about
the CLASS implementation.  I suspect BT_CLASS takes a much
different path through the compiler.

  parent reply	other threads:[~2021-09-15 21:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14 17:29 [Bug fortran/102331] New: " gscfq@t-online.de
2021-09-14 17:29 ` [Bug fortran/102331] " gscfq@t-online.de
2021-09-15  8:51 ` marxin at gcc dot gnu.org
2021-09-15 17:20 ` kargl at gcc dot gnu.org
2021-09-15 20:57 ` anlauf at gcc dot gnu.org
2021-09-15 21:59 ` sgk at troutmask dot apl.washington.edu [this message]
2022-12-26 19:55 ` jvdelisle at gcc dot gnu.org
2022-12-26 20:14 ` jvdelisle at gcc dot gnu.org
2023-01-14  3:29 ` jvdelisle at gcc dot gnu.org
2023-01-18  1:37 ` jvdelisle at gcc dot gnu.org
2023-03-27  2:00 ` cvs-commit at gcc dot gnu.org
2023-05-29 22:06 ` kargl 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-102331-4-xZmxI76Mdr@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).