public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/58331] [OOP] Bogus rank checking with explicit-/assumed-size arrays and CLASS Date: Thu, 09 Mar 2023 19:44:36 +0000 [thread overview] Message-ID: <bug-58331-4-jVLWsMlXhC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58331-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58331 --- Comment #7 from anlauf at gcc dot gnu.org --- Created attachment 54627 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54627&action=edit Latest patch This patch fixes the testcases in this PR. I tried other testcases that use coarrays, but e.g. the following scalar coarray case produces an ICE later on. I believe this is a pre-existing separate issue. program p implicit none integer :: ca[*] ca = 2 call sub_ca(ca) contains subroutine sub_ca (a) class(*), intent(in) :: a[*] end end pr58331-ca.f90:8:17: 8 | call sub_ca(ca) | 1 internal compiler error: in fold_convert_loc, at fold-const.cc:2627 0x726047 fold_convert_loc(unsigned int, tree_node*, tree_node*) ../../gcc-trunk/gcc/fold-const.cc:2627 0xa5edd2 gfc_conv_intrinsic_to_class(gfc_se*, gfc_expr*, gfc_typespec) ../../gcc-trunk/gcc/fortran/trans-expr.cc:1040 0xa70271 gfc_conv_procedure_call(gfc_se*, gfc_symbol*, gfc_actual_arglist*, gfc_expr*, vec<tree_node*, va_gc, vl_embed>*) ../../gcc-trunk/gcc/fortran/trans-expr.cc:6239 0xadef24 gfc_trans_call(gfc_code*, bool, tree_node*, tree_node*, bool) ../../gcc-trunk/gcc/fortran/trans-stmt.cc:424 0xa0f555 trans_code ../../gcc-trunk/gcc/fortran/trans.cc:2018 0xa0fa1a gfc_trans_code(gfc_code*) ../../gcc-trunk/gcc/fortran/trans.cc:2303 0xa586b0 gfc_generate_function_code(gfc_namespace*) ../../gcc-trunk/gcc/fortran/trans-decl.cc:7704 0xa0fa5e gfc_generate_code(gfc_namespace*) ../../gcc-trunk/gcc/fortran/trans.cc:2320 0x9a5de6 translate_all_program_units ../../gcc-trunk/gcc/fortran/parse.cc:6720 0x9a66e8 gfc_parse_file() ../../gcc-trunk/gcc/fortran/parse.cc:7026 0x9f6d5e gfc_be_parse_file ../../gcc-trunk/gcc/fortran/f95-lang.cc:229
next prev parent reply other threads:[~2023-03-09 19:44 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-06 6:00 [Bug fortran/58331] New: " burnus at gcc dot gnu.org 2013-09-06 21:35 ` [Bug fortran/58331] " burnus at gcc dot gnu.org 2013-09-08 16:46 ` burnus at gcc dot gnu.org 2014-03-22 15:02 ` dominiq at lps dot ens.fr 2023-03-06 21:43 ` anlauf at gcc dot gnu.org 2023-03-06 22:13 ` anlauf at gcc dot gnu.org 2023-03-07 9:14 ` burnus at gcc dot gnu.org 2023-03-09 19:44 ` anlauf at gcc dot gnu.org [this message] 2023-03-14 19:39 ` anlauf at gcc dot gnu.org 2023-03-15 8:58 ` burnus at gcc dot gnu.org 2023-03-15 19:22 ` cvs-commit at gcc dot gnu.org 2023-03-15 20:03 ` 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-58331-4-jVLWsMlXhC@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).