public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/89645] No IMPLICIT type error with: ASSOCIATE( X => function() )
Date: Fri, 02 Jun 2023 08:10:13 +0000	[thread overview]
Message-ID: <bug-89645-4-H2ncyTJk6Y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-89645-4@http.gcc.gnu.org/bugzilla/>

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

Paul Thomas <pault at gcc dot gnu.org> changed:

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

--- Comment #2 from Paul Thomas <pault at gcc dot gnu.org> ---
Hi Ian,

This is one of two PRs (cf. 99065) that expose a really nasty fault with
gfortran parsing. If you interchange 's' and 'fun', you will find that the
testcase compiles and runs.

The fixup for intrinsic types works fine but, unfortunately, the derived type
is need for parsing the associate block itself.

I am girding my loins to fight the good fight.

Thanks for this posting.

Paul

       reply	other threads:[~2023-06-02  8:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-89645-4@http.gcc.gnu.org/bugzilla/>
2023-06-02  8:10 ` pault at gcc dot gnu.org [this message]
2023-06-28 16:39 ` pault at gcc dot gnu.org
2023-12-03 10:40 ` pault at gcc dot gnu.org
2023-12-16 10:39 ` pault at gcc dot gnu.org
2024-03-15  6:53 ` cvs-commit at gcc dot gnu.org
2024-03-15  7:07 ` pault 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-89645-4-H2ncyTJk6Y@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).