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/105243] ICE in next_char, at fortran/io.cc:160 Date: Tue, 12 Apr 2022 17:22:03 +0000 [thread overview] Message-ID: <bug-105243-4-8SvXBmfbMH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105243-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105243 G. Steinmetz <gscfq@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-invalid-code --- Comment #1 from G. Steinmetz <gscfq@t-online.de> --- $ cat z2.f90 program p type t character(3) :: c = '(a)' end type class(t), parameter :: x = 1. print *, x%c end $ cat z3.f90 program p type t character(3) :: c = '(a)' end type class(t), parameter :: x = 1. call s(x%c) end $ gfortran-12-20220410 -c z2.f90 z2.f90:5:27: 5 | class(t), parameter :: x = 1. | 1 Error: CLASS variable 'x' at (1) cannot have the PARAMETER attribute z2.f90:5:29: 5 | class(t), parameter :: x = 1. | 1 Error: Cannot convert REAL(4) to CLASS() at (1) f951: internal compiler error: Segmentation fault 0xe7751f crash_signal ../../gcc/toplev.cc:322 0x734da3 free_expr0 ../../gcc/fortran/expr.cc:462 0x734e48 gfc_free_expr(gfc_expr*) ../../gcc/fortran/expr.cc:531 0x7cfd51 gfc_free_statement(gfc_code*) ../../gcc/fortran/st.cc:86 0x7cfef2 gfc_free_statements(gfc_code*) ../../gcc/fortran/st.cc:318 0x7cff14 gfc_free_statements(gfc_code*) ../../gcc/fortran/st.cc:317 0x7d6a24 gfc_free_namespace(gfc_namespace*&) ../../gcc/fortran/symbol.cc:4041 0x7d7159 gfc_symbol_done_2() ../../gcc/fortran/symbol.cc:4105 0x76e548 gfc_done_2() ../../gcc/fortran/misc.cc:382 0x798198 translate_all_program_units ../../gcc/fortran/parse.cc:6688 0x798198 gfc_parse_file() ../../gcc/fortran/parse.cc:6956 0x7e626f gfc_be_parse_file ../../gcc/fortran/f95-lang.cc:216
next prev parent reply other threads:[~2022-04-12 17:22 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-12 17:21 [Bug fortran/105243] New: " gscfq@t-online.de 2022-04-12 17:22 ` gscfq@t-online.de [this message] 2022-05-16 0:06 ` [Bug fortran/105243] " kargl at gcc dot gnu.org 2022-05-16 20:27 ` anlauf at gcc dot gnu.org 2022-05-16 21:06 ` anlauf at gcc dot gnu.org 2022-05-16 22:16 ` sgk at troutmask dot apl.washington.edu 2022-05-16 22:22 ` sgk at troutmask dot apl.washington.edu 2022-05-17 19:56 ` anlauf at gcc dot gnu.org 2022-05-17 23:21 ` sgk at troutmask dot apl.washington.edu 2022-06-29 19:42 ` anlauf at gcc dot gnu.org 2022-06-29 19:54 ` anlauf at gcc dot gnu.org 2022-06-29 20:27 ` sgk at troutmask dot apl.washington.edu 2022-06-30 19:01 ` cvs-commit at gcc dot gnu.org 2022-07-03 19:44 ` cvs-commit at gcc dot gnu.org 2022-07-03 20:13 ` cvs-commit at gcc dot gnu.org 2022-07-03 20:29 ` cvs-commit at gcc dot gnu.org 2022-07-03 20:33 ` anlauf 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-105243-4-8SvXBmfbMH@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).