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/103138] New: [12 Regression] ICE in gfc_simplify_cshift, at fortran/simplify.c:2139 Date: Mon, 08 Nov 2021 18:38:52 +0000 [thread overview] Message-ID: <bug-103138-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103138 Bug ID: 103138 Summary: [12 Regression] ICE in gfc_simplify_cshift, at fortran/simplify.c:2139 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Also changed between 20211031 and 20211107 : (related to pr103137) $ cat z1.f90 program p type t end type class(t), parameter :: a(2) = 2 integer, parameter :: b(2) = cshift(a, 1) end $ gfortran-12-20211031 -c z1.f90 z1.f90:4:30: 4 | class(t), parameter :: a(2) = 2 | 1 Error: CLASS variable 'a' at (1) cannot have the PARAMETER attribute z1.f90:4:32: 4 | class(t), parameter :: a(2) = 2 | 1 Error: Cannot convert INTEGER(4) to invalid class at (1) $ gfortran-12-20211107 -c z1.f90 f951: internal compiler error: Segmentation fault 0xd4f7bf crash_signal ../../gcc/toplev.c:322 0x826574 gfc_simplify_cshift(gfc_expr*, gfc_expr*, gfc_expr*) ../../gcc/fortran/simplify.c:2139 0x7aa917 do_simplify ../../gcc/fortran/intrinsic.c:4672 0x7b52ea gfc_intrinsic_func_interface(gfc_expr*, int) ../../gcc/fortran/intrinsic.c:5051 0x808bec resolve_unknown_f ../../gcc/fortran/resolve.c:2972 0x808bec resolve_function ../../gcc/fortran/resolve.c:3329 0x808bec gfc_resolve_expr(gfc_expr*) ../../gcc/fortran/resolve.c:7166 0x79a754 gfc_reduce_init_expr(gfc_expr*) ../../gcc/fortran/expr.c:3130 0x79d620 gfc_match_init_expr(gfc_expr**) ../../gcc/fortran/expr.c:3178 0x787bf4 variable_decl ../../gcc/fortran/decl.c:3004 0x787bf4 gfc_match_data_decl() ../../gcc/fortran/decl.c:6297 0x7f12c3 match_word ../../gcc/fortran/parse.c:67 0x7f12c3 decode_statement ../../gcc/fortran/parse.c:378 0x7f2d0a next_free ../../gcc/fortran/parse.c:1388 0x7f2d0a next_statement ../../gcc/fortran/parse.c:1620 0x7f442b parse_spec ../../gcc/fortran/parse.c:4159 0x7f779c parse_progunit ../../gcc/fortran/parse.c:6170 0x7f8a71 gfc_parse_file() ../../gcc/fortran/parse.c:6715 0x845d3f gfc_be_parse_file ../../gcc/fortran/f95-lang.c:216
next reply other threads:[~2021-11-08 18:38 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-08 18:38 gscfq@t-online.de [this message] 2021-11-08 20:40 ` [Bug fortran/103138] " anlauf at gcc dot gnu.org 2021-11-08 22:17 ` anlauf at gcc dot gnu.org 2021-11-09 8:33 ` [Bug fortran/103138] [12 Regression] ICE in gfc_simplify_cshift, at fortran/simplify.c:2139 since r12-4967-gbcf3728abe848888 marxin at gcc dot gnu.org 2021-11-09 11:24 ` rguenth at gcc dot gnu.org 2021-11-10 19:42 ` cvs-commit at gcc dot gnu.org 2021-11-11 20:17 ` cvs-commit at gcc dot gnu.org 2021-11-13 20:15 ` cvs-commit at gcc dot gnu.org 2022-05-06 8:31 ` [Bug fortran/103138] [12/13 " jakub at gcc dot gnu.org 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:31 ` 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-103138-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).