public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/106946] New: [10/11/12/13 Regression] ICE in resolve_component, at fortran/resolve.cc:14726 Date: Wed, 14 Sep 2022 18:53:45 +0000 [thread overview] Message-ID: <bug-106946-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106946 Bug ID: 106946 Summary: [10/11/12/13 Regression] ICE in resolve_component, at fortran/resolve.cc:14726 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started with r9 between 20180819 and 20180826 : $ cat z1.f90 program p type t class(u), allocatable :: a b end type end $ cat z2.f90 module m type t class(u), allocatable :: a b end type end $ gfortran-9-20180819 -c z1.f90 z1.f90:3:30: 3 | class(u), allocatable :: a b | 1 Error: Derived type at (1) has not been previously defined and so cannot appear in a derived type definition $ gfortran-13-20220911 -c z1.f90 z1.f90:3:33: 3 | class(u), allocatable :: a b | 1 Error: Syntax error in data declaration at (1) z1.f90:1:9: 1 | program p | 1 Error: Argument 'src' of '_copy' with PASS(src) at (1) must be of the derived type '__class_p_U_a' f951: internal compiler error: Segmentation fault 0xf386bf crash_signal ../../gcc/toplev.cc:314 0x8781c2 resolve_component ../../gcc/fortran/resolve.cc:14726 0x878ca2 resolve_fl_derived0 ../../gcc/fortran/resolve.cc:15075 0x878fed resolve_fl_derived ../../gcc/fortran/resolve.cc:15207 0x872a67 resolve_symbol ../../gcc/fortran/resolve.cc:15584 0x891d72 do_traverse_symtree ../../gcc/fortran/symbol.cc:4174 0x876034 resolve_types ../../gcc/fortran/resolve.cc:17534 0x8714ac gfc_resolve(gfc_namespace*) ../../gcc/fortran/resolve.cc:17649 0x8592a4 resolve_all_program_units ../../gcc/fortran/parse.cc:6606 0x8592a4 gfc_parse_file() ../../gcc/fortran/parse.cc:6862 0x8a7c6f gfc_be_parse_file ../../gcc/fortran/f95-lang.cc:229
next reply other threads:[~2022-09-14 18:53 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-14 18:53 gscfq@t-online.de [this message] 2022-09-14 19:59 ` [Bug fortran/106946] " marxin at gcc dot gnu.org 2022-09-15 7:18 ` rguenth at gcc dot gnu.org 2023-02-28 20:41 ` anlauf at gcc dot gnu.org 2023-07-07 10:43 ` [Bug fortran/106946] [11/12/13/14 " rguenth 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-106946-4@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).