public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93678] [11/12/13/14 Regression] ICE with TRANSFER and typebound procedures
Date: Thu, 25 Apr 2024 05:56:48 +0000 [thread overview]
Message-ID: <bug-93678-4-yLfP6VeuGk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93678-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93678
--- Comment #15 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Paul Thomas <pault@gcc.gnu.org>:
https://gcc.gnu.org/g:c058105bc47a0701e157d1028e60f48554561f9f
commit r14-10116-gc058105bc47a0701e157d1028e60f48554561f9f
Author: Paul Thomas <pault@gcc.gnu.org>
Date: Thu Apr 25 06:56:10 2024 +0100
Fortran: Fix ICE in gfc_trans_create_temp_array from bad type [PR93678]
2024-04-25 Paul Thomas <pault@gcc.gnu.org>
gcc/fortran
PR fortran/93678
* trans-expr.cc (gfc_conv_procedure_call): Use the interface,
where possible, to obtain the type of character procedure
pointers of class entities.
gcc/testsuite/
PR fortran/93678
* gfortran.dg/pr93678.f90: New test.
next prev parent reply other threads:[~2024-04-25 5:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-93678-4@http.gcc.gnu.org/bugzilla/>
2020-07-12 12:34 ` [Bug fortran/93678] [9/10/11 Regression] ICE in 9.2/9.2.1 not happening in previous gfortran versions tkoenig at gcc dot gnu.org
2020-07-12 12:55 ` tkoenig at gcc dot gnu.org
2020-07-12 13:08 ` [Bug fortran/93678] [9/10/11 Regression] ICE with TRANSFER and typebound procedures tkoenig at gcc dot gnu.org
2020-10-30 20:31 ` [Bug fortran/93678] [8/9/10/11 " anlauf at gcc dot gnu.org
2020-10-30 20:48 ` anlauf at gcc dot gnu.org
2020-10-30 21:03 ` anlauf at gcc dot gnu.org
2021-06-01 8:16 ` [Bug fortran/93678] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-05-27 9:42 ` [Bug fortran/93678] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:39 ` jakub at gcc dot gnu.org
2023-07-07 10:36 ` [Bug fortran/93678] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-04-24 15:49 ` pault at gcc dot gnu.org
2024-04-25 5:56 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-25 6:00 ` [Bug fortran/93678] [11/12/13 " pault at gcc dot gnu.org
2024-05-08 8:11 ` cvs-commit at gcc dot gnu.org
2024-05-08 8:12 ` 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-93678-4-yLfP6VeuGk@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).