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/96024] New: [9/10/11 Regression] ICE in mio_name_expr_t, at fortran/module.c:2159 Date: Wed, 01 Jul 2020 19:30:29 +0000 [thread overview] Message-ID: <bug-96024-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96024 Bug ID: 96024 Summary: [9/10/11 Regression] ICE in mio_name_expr_t, at fortran/module.c:2159 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- This invalid code (character char(n) is not a legal len value) gives an ICE down to r6, seems to be accepted by r5 : $ cat z1.f90 module m type t character(char(1)) :: a end type type(t) :: z = t('a') end $ gfortran-5 -c z1.f90 $ $ gfortran-11-20200628 -c z1.f90 f951: internal compiler error: Segmentation fault 0xbd215f crash_signal ../../gcc/toplev.c:328 0x696d8c mio_name_expr_t ../../gcc/fortran/module.c:2159 0x696d8c mio_expr ../../gcc/fortran/module.c:3567 0x697543 mio_charlen ../../gcc/fortran/module.c:2629 0x69763c mio_typespec ../../gcc/fortran/module.c:2687 0x696da0 mio_expr ../../gcc/fortran/module.c:3586 0x697543 mio_charlen ../../gcc/fortran/module.c:2629 0x69763c mio_typespec ../../gcc/fortran/module.c:2687 0x6979c5 mio_component ../../gcc/fortran/module.c:2920 0x6989da mio_component_list ../../gcc/fortran/module.c:2957 0x6989da mio_symbol ../../gcc/fortran/module.c:4416 0x698e3d write_symbol ../../gcc/fortran/module.c:5771 0x698fa2 write_symbol0 ../../gcc/fortran/module.c:5811 0x698f18 write_symbol0 ../../gcc/fortran/module.c:5790 0x698f18 write_symbol0 ../../gcc/fortran/module.c:5790 0x69bb04 write_module ../../gcc/fortran/module.c:6153 0x69bb04 dump_module ../../gcc/fortran/module.c:6283 0x69becd gfc_dump_module(char const*, int) ../../gcc/fortran/module.c:6340 0x6b5d26 gfc_parse_file() ../../gcc/fortran/parse.c:6457 0x7016ff gfc_be_parse_file ../../gcc/fortran/f95-lang.c:212
next reply other threads:[~2020-07-01 19:30 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-01 19:30 gscfq@t-online.de [this message] 2020-07-01 20:11 ` [Bug fortran/96024] " dominiq at lps dot ens.fr 2020-07-01 21:30 ` kargl at gcc dot gnu.org 2020-07-01 21:30 ` kargl at gcc dot gnu.org 2020-07-02 6:42 ` rguenth at gcc dot gnu.org 2020-07-04 9:29 ` dominiq at lps dot ens.fr 2020-07-04 14:24 ` sgk at troutmask dot apl.washington.edu 2020-07-24 5:17 ` tkoenig at gcc dot gnu.org 2020-07-24 15:30 ` kargl at gcc dot gnu.org 2021-06-01 8:17 ` [Bug fortran/96024] [9/10/11/12 " rguenth at gcc dot gnu.org 2022-05-27 9:42 ` [Bug fortran/96024] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:41 ` jakub at gcc dot gnu.org 2023-02-21 20:46 ` anlauf at gcc dot gnu.org 2023-02-21 21:28 ` anlauf at gcc dot gnu.org 2023-02-22 17:56 ` cvs-commit at gcc dot gnu.org 2023-03-04 19:51 ` cvs-commit at gcc dot gnu.org 2023-03-05 19:35 ` cvs-commit at gcc dot gnu.org 2023-03-05 19:36 ` cvs-commit at gcc dot gnu.org 2023-03-05 19:38 ` anlauf at gcc dot gnu.org 2023-03-05 19:39 ` anlauf at gcc dot gnu.org 2023-06-08 8:51 ` jakub at gcc dot gnu.org 2023-06-08 9:42 ` anlauf at gcc dot gnu.org 2023-06-09 7:14 ` cvs-commit at gcc dot gnu.org 2023-06-09 7:21 ` cvs-commit at gcc dot gnu.org 2023-06-09 7:58 ` cvs-commit at gcc dot gnu.org 2023-06-09 8:00 ` cvs-commit at gcc dot gnu.org 2023-06-09 8:01 ` cvs-commit at gcc dot gnu.org 2023-06-09 8:45 ` jakub 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-96024-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).