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/99818] New: [10/11 Regression] ICE in gfc_get_tree_for_caf_expr, at fortran/trans-expr.c:2186 Date: Mon, 29 Mar 2021 19:33:38 +0000 [thread overview] Message-ID: <bug-99818-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99818 Bug ID: 99818 Summary: [10/11 Regression] ICE in gfc_get_tree_for_caf_expr, at fortran/trans-expr.c:2186 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: --- Changed between 20210207 and 20210214 : $ cat z1.f90 module m type t integer :: a contains procedure :: s end type contains subroutine s(x) class(t) :: x[*] end end program p use m associate (y => t(1)) call y%s end associate end $ gfortran-11-20210207 -c z1.f90 -fcoarray=single z1.f90:15:12: 15 | call y%s | 1 Error: VARIABLE attribute of 'y' conflicts with PROCEDURE attribute at (1) $ gfortran-11-20210207 -c z1.f90 -fcoarray=lib z1.f90:15:12: 15 | call y%s | 1 Error: VARIABLE attribute of 'y' conflicts with PROCEDURE attribute at (1) $ gfortran-11-20210328 -c z1.f90 -fcoarray=single $ $ gfortran-11-20210328 -c z1.f90 -fcoarray=lib z1.f90:15:14: 15 | call y%s | 1 internal compiler error: in gfc_get_tree_for_caf_expr, at fortran/trans-expr.c:2186 0x76304b gfc_get_tree_for_caf_expr(gfc_expr*) ../../gcc/fortran/trans-expr.c:2186 0x76fb7b gfc_conv_procedure_call(gfc_se*, gfc_symbol*, gfc_actual_arglist*, gfc_expr*, vec<tree_node*, va_gc, vl_embed>*) ../../gcc/fortran/trans-expr.c:6837 0x7a8d28 gfc_trans_call(gfc_code*, bool, tree_node*, tree_node*, bool) ../../gcc/fortran/trans-stmt.c:424 0x7391a8 trans_code ../../gcc/fortran/trans.c:1990 0x7ad12f gfc_trans_block_construct(gfc_code*) ../../gcc/fortran/trans-stmt.c:2304 0x738f67 trans_code ../../gcc/fortran/trans.c:2018 0x75f5e4 gfc_generate_function_code(gfc_namespace*) ../../gcc/fortran/trans-decl.c:6884 0x6e5de6 translate_all_program_units ../../gcc/fortran/parse.c:6351 0x6e5de6 gfc_parse_file() ../../gcc/fortran/parse.c:6620 0x7320ef gfc_be_parse_file ../../gcc/fortran/f95-lang.c:212
next reply other threads:[~2021-03-29 19:33 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-29 19:33 gscfq@t-online.de [this message] 2021-03-30 13:08 ` [Bug fortran/99818] " rguenth at gcc dot gnu.org 2021-03-31 12:49 ` marxin at gcc dot gnu.org 2021-03-31 13:24 ` pault at gcc dot gnu.org 2021-04-01 13:34 ` pault at gcc dot gnu.org 2021-04-03 9:19 ` gscfq@t-online.de 2021-04-03 11:50 ` cvs-commit at gcc dot gnu.org 2021-04-05 6:21 ` pault at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2021-05-04 12:31 ` [Bug fortran/99818] [10/11/12 " rguenth at gcc dot gnu.org 2021-08-28 20:05 ` cvs-commit at gcc dot gnu.org 2021-08-28 20:06 ` anlauf 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-99818-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).