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/93678] [11/12/13/14 Regression] ICE with TRANSFER and typebound procedures Date: Wed, 24 Apr 2024 15:49:38 +0000 [thread overview] Message-ID: <bug-93678-4-XlWAJ4AMt6@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 Paul Thomas <pault at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org CC| |pault at gcc dot gnu.org --- Comment #14 from Paul Thomas <pault at gcc dot gnu.org> --- Created attachment 58026 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58026&action=edit Fix for this PR I'll package it all up for the list in the next 24 hours. Regtests OK, the testcase of comment 1 compiles and this runs fine: ! { dg-do compile } ! Test the fix for PR93678 in which the charlen for the 'unpackbytes' ! vtable field was incomplete and caused the ICE as indicated. ! Contributed by Luis Kornblueh <mail.luis@web.de> ! ! The testcase was reduced by various gfortran regulars. module mo_a implicit none type t_b integer :: i contains procedure :: unpackbytes => b_unpackbytes end type t_b contains function b_unpackbytes (me) result (res) class(t_b), intent(inout) :: me character :: res(1) res = char (me%i) end function b_unpackbytes subroutine b_unpackint (me, c) class(t_b), intent(inout) :: me character, intent(in) :: c ! print *, b_unpackbytes (me) ! ok if (any (me% unpackbytes () .ne. c)) stop 1 ! ICEd here end subroutine b_unpackint end module mo_a use mo_a class(t_b), allocatable :: z allocate (z, source = t_b(97)) call b_unpackint (z, "a") end
next prev parent reply other threads:[~2024-04-24 15:49 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 [this message] 2024-04-25 5:56 ` cvs-commit at gcc dot gnu.org 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-XlWAJ4AMt6@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: linkBe 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).