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/100156] New: ICE in gfc_trans_array_cobounds, at fortran/trans-array.c:6257 Date: Tue, 20 Apr 2021 17:41:02 +0000 [thread overview] Message-ID: <bug-100156-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100156 Bug ID: 100156 Summary: ICE in gfc_trans_array_cobounds, at fortran/trans-array.c:6257 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: --- With option -fcoarray=single, affects versions down to at least r5 : (compiles with -fcoarray=lib) (compiles always without attribute volatile) $ cat z1.f90 program p integer, volatile :: a = 1 integer, volatile :: b[*] = 1 if (a /= b) stop end $ gfortran-11-20210418 -c z1.f90 -fcoarray=lib $ $ gfortran-11-20210418 -c z1.f90 -fcoarray=single z1.f90:5:3: 5 | end | 1 internal compiler error: Segmentation fault 0xc0b22f crash_signal ../../gcc/toplev.c:327 0x7425b1 gfc_trans_array_cobounds(tree_node*, stmtblock_t*, gfc_symbol const*) ../../gcc/fortran/trans-array.c:6257 0x75e271 gfc_trans_deferred_vars(gfc_symbol*, gfc_wrapped_block*) ../../gcc/fortran/trans-decl.c:4858 0x75fe22 gfc_generate_function_code(gfc_namespace*) ../../gcc/fortran/trans-decl.c:6988 0x6e66b6 translate_all_program_units ../../gcc/fortran/parse.c:6351 0x6e66b6 gfc_parse_file() ../../gcc/fortran/parse.c:6620 0x7329cf gfc_be_parse_file ../../gcc/fortran/f95-lang.c:212
next reply other threads:[~2021-04-20 17:41 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-20 17:41 gscfq@t-online.de [this message] 2021-04-21 6:21 ` [Bug fortran/100156] " marxin 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-100156-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).