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/96013] New: ICE in write_symbol, at fortran/module.c:5747 Date: Tue, 30 Jun 2020 20:12:15 +0000 [thread overview] Message-ID: <bug-96013-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96013 Bug ID: 96013 Summary: ICE in write_symbol, at fortran/module.c:5747 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: --- Affects versions down to at least r5 : $ cat z1.f90 module m type t end type contains function f() result(t) character(3) :: c c = 'abc' end end $ gfortran-11-20200628 -c z1.f90 ' Segmentation fault 0xbd215f crash_signal ../../gcc/toplev.c:328 0x61891e pp_quoted_string ../../gcc/pretty-print.c:1845 0x1504b93 pp_format(pretty_printer*, text_info*) ../../gcc/pretty-print.c:1359 0x14f96df diagnostic_report_diagnostic(diagnostic_context*, diagnostic_info*) ../../gcc/diagnostic.c:1159 0x657489 gfc_report_diagnostic ../../gcc/fortran/error.c:782 0x658baa gfc_internal_error(char const*, ...) ../../gcc/fortran/error.c:1402 0x698e80 write_symbol ../../gcc/fortran/module.c:5747 0x698ecb write_symbol1_recursion ../../gcc/fortran/module.c:5974 0x69bb35 write_symbol1 ../../gcc/fortran/module.c:6007 0x69bb35 write_module ../../gcc/fortran/module.c:6154 0x69bb35 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-06-30 20:12 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-30 20:12 gscfq@t-online.de [this message] 2020-06-30 20:12 ` [Bug fortran/96013] " gscfq@t-online.de 2020-06-30 20:47 ` kargl at gcc dot gnu.org 2020-06-30 21:00 ` kargl at gcc dot gnu.org 2020-06-30 21:22 ` kargl at gcc dot gnu.org 2020-06-30 21:38 ` kargl at gcc dot gnu.org 2020-06-30 21:41 ` kargl at gcc dot gnu.org 2021-03-26 12:08 ` dominiq at lps dot ens.fr 2021-03-26 16:04 ` kargl at gcc dot gnu.org 2021-03-26 16:30 ` dominiq at lps dot ens.fr 2021-03-26 17:12 ` kargl at gcc dot gnu.org 2021-03-27 13:56 ` dominiq at lps dot ens.fr 2021-03-27 13:59 ` dominiq at lps dot ens.fr 2021-04-18 11:27 ` dominiq at lps dot ens.fr 2021-04-18 17:34 ` kargl 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-96013-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).