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/106999] [11/12/13/14 Regression] ICE tree check: expected record_type or union_type or qual_union_type, have function_type in gfc_class_data_get, at fortran/trans-expr.cc:233
Date: Sun, 31 Mar 2024 12:16:32 +0000	[thread overview]
Message-ID: <bug-106999-4-pHc4WkFpDb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106999-4@http.gcc.gnu.org/bugzilla/>

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

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

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

--- Comment #5 from Paul Thomas <pault at gcc dot gnu.org> ---
Created attachment 57838
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57838&action=edit
Fix for this PR

Thanks for the report. The attached does what is required, I believe. It is
regtesting as I write.

Paul

  parent reply	other threads:[~2024-03-31 12:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 17:32 [Bug fortran/106999] New: [11/12/13 " gscfq@t-online.de
2022-09-21 17:32 ` [Bug fortran/106999] " gscfq@t-online.de
2022-09-22  6:48 ` rguenth at gcc dot gnu.org
2022-09-22 19:22 ` marxin at gcc dot gnu.org
2023-04-17 19:42 ` [Bug fortran/106999] [11/12/13/14 " anlauf at gcc dot gnu.org
2023-05-29 10:07 ` jakub at gcc dot gnu.org
2024-03-31 12:16 ` pault at gcc dot gnu.org [this message]
2024-04-02 14:53 ` cvs-commit at gcc dot gnu.org
2024-04-23  9:49 ` [Bug fortran/106999] [11/12/13 " pault at gcc dot gnu.org
2024-05-06  9:57 ` cvs-commit at gcc dot gnu.org
2024-05-06 10:01 ` cvs-commit at gcc dot gnu.org
2024-05-06 10:03 ` 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-106999-4-pHc4WkFpDb@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).