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/95504] New: ICE in transfer_array_component, at fortran/trans-io.c:2167 Date: Wed, 03 Jun 2020 15:47:22 +0000 [thread overview] Message-ID: <bug-95504-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95504 Bug ID: 95504 Summary: ICE in transfer_array_component, at fortran/trans-io.c:2167 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: --- Started with r8 before 20180525 : $ cat z1.f90 program p type t(n) integer, len :: n integer, pointer :: a(:) end type type(t(3)) :: z print *, z end $ cat z2.f90 program p type t(n) integer, len :: n integer, allocatable :: a(:) end type type(t(3)) :: z print *, z end $ gfortran-11-20200531 -c z1.f90 z1.f90:7:0: 7 | print *, z | internal compiler error: Segmentation fault 0xbc37bf crash_signal ../../gcc/toplev.c:328 0x75e576 transfer_array_component ../../gcc/fortran/trans-io.c:2167 0x75de47 transfer_expr ../../gcc/fortran/trans-io.c:2471 0x7616a0 gfc_trans_transfer(gfc_code*) ../../gcc/fortran/trans-io.c:2661 0x7017f7 trans_code ../../gcc/fortran/trans.c:2084 0x75f16e build_dt ../../gcc/fortran/trans-io.c:2026 0x7017d7 trans_code ../../gcc/fortran/trans.c:2056 0x72ad24 gfc_generate_function_code(gfc_namespace*) ../../gcc/fortran/trans-decl.c:6840 0x6b25e6 translate_all_program_units ../../gcc/fortran/parse.c:6306 0x6b25e6 gfc_parse_file() ../../gcc/fortran/parse.c:6545 0x6fdfff gfc_be_parse_file ../../gcc/fortran/f95-lang.c:210
next reply other threads:[~2020-06-03 15:47 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-03 15:47 gscfq@t-online.de [this message] 2020-06-03 15:48 ` [Bug fortran/95504] " gscfq@t-online.de 2020-06-03 18:43 ` [Bug fortran/95504] [PDT] " anlauf at gcc dot gnu.org 2023-06-30 8:12 ` pault 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-95504-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).