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/101100] New: [9/10/11/12 Regression] ICE in trans_caf_token_assign, at fortran/trans-expr.c:9433 Date: Wed, 16 Jun 2021 17:22:31 +0000 [thread overview] Message-ID: <bug-101100-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101100 Bug ID: 101100 Summary: [9/10/11/12 Regression] ICE in trans_caf_token_assign, at fortran/trans-expr.c:9433 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: --- Affects versions down to r7 : $ cat z1.f90 program p type t procedure(), pointer, nopass :: f end type type(t) :: x[*] x%f => null() end $ gfortran-6 -c z1.f90 -fcoarray=lib $ gfortran-12-20210613 -c z1.f90 -fcoarray=single $ $ gfortran-12-20210613 -c z1.f90 -fcoarray=lib z1.f90:6:16: 6 | x%f => null() | 1 internal compiler error: Segmentation fault 0xc7bfff crash_signal ../../gcc/toplev.c:327 0x9a9f57 build_fold_indirect_ref_loc(unsigned int, tree_node*) ../../gcc/fold-const.c:15991 0x7dd4d6 trans_caf_token_assign ../../gcc/fortran/trans-expr.c:9433 0x7dd4d6 gfc_trans_pointer_assignment(gfc_expr*, gfc_expr*) ../../gcc/fortran/trans-expr.c:9586 0x79f8c7 trans_code ../../gcc/fortran/trans.c:1926 0x7c6054 gfc_generate_function_code(gfc_namespace*) ../../gcc/fortran/trans-decl.c:6893 0x74c876 translate_all_program_units ../../gcc/fortran/parse.c:6461 0x74c876 gfc_parse_file() ../../gcc/fortran/parse.c:6730 0x798bbf gfc_be_parse_file ../../gcc/fortran/f95-lang.c:212
next reply other threads:[~2021-06-16 17:22 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-16 17:22 gscfq@t-online.de [this message] 2021-06-17 6:39 ` [Bug fortran/101100] " rguenth at gcc dot gnu.org 2021-06-17 9:34 ` marxin at gcc dot gnu.org 2022-01-17 14:31 ` rguenth at gcc dot gnu.org 2022-05-27 9:45 ` [Bug fortran/101100] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:45 ` jakub at gcc dot gnu.org 2023-07-07 10:40 ` [Bug fortran/101100] [11/12/13/14 " rguenth 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-101100-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).