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/107444] New: ICE on character, value, optional dummy argument Date: Thu, 27 Oct 2022 21:06:02 +0000 [thread overview] Message-ID: <bug-107444-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107444 Bug ID: 107444 Summary: ICE on character, value, optional dummy argument Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: anlauf at gcc dot gnu.org Target Milestone: --- The following ICE was found while working on PR107441: subroutine test (w) character, value, optional :: w print *, present (w) end pr107441-yy.f90:3:22: 3 | print *, present (w) | 1 internal compiler error: in fold_convert_loc, at fold-const.cc:2592 0xf10c3d fold_convert_loc(unsigned int, tree_node*, tree_node*) ../../gcc-trunk/gcc/fold-const.cc:2592 0xc2be3a gfc_conv_expr_present(gfc_symbol*, bool) ../../gcc-trunk/gcc/fortran/trans-expr.cc:2023 0xc5d01f gfc_conv_intrinsic_present ../../gcc-trunk/gcc/fortran/trans-intrinsic.cc:3669 0xc73567 gfc_conv_intrinsic_function(gfc_se*, gfc_expr*) ../../gcc-trunk/gcc/fortran/trans-intrinsic.cc:10882 0xc4264b gfc_conv_function_expr ../../gcc-trunk/gcc/fortran/trans-expr.cc:8312 0xc4651f gfc_conv_expr(gfc_se*, gfc_expr*) ../../gcc-trunk/gcc/fortran/trans-expr.cc:9452 0xc46a14 gfc_conv_expr_reference(gfc_se*, gfc_expr*) ../../gcc-trunk/gcc/fortran/trans-expr.cc:9588 0xc81f47 gfc_trans_transfer(gfc_code*) ../../gcc-trunk/gcc/fortran/trans-io.cc:2607 0xbd9a31 trans_code ../../gcc-trunk/gcc/fortran/trans.cc:2170 0xbd9ba3 gfc_trans_code_cond(gfc_code*, tree_node*) ../../gcc-trunk/gcc/fortran/trans.cc:2295 0xc80889 build_dt ../../gcc-trunk/gcc/fortran/trans-io.cc:2051 0xc80961 gfc_trans_write(gfc_code*) ../../gcc-trunk/gcc/fortran/trans-io.cc:2090 0xbd99a7 trans_code ../../gcc-trunk/gcc/fortran/trans.cc:2142 0xbd9bc2 gfc_trans_code(gfc_code*) ../../gcc-trunk/gcc/fortran/trans.cc:2303 0xc224d1 gfc_generate_function_code(gfc_namespace*) ../../gcc-trunk/gcc/fortran/trans-decl.cc:7666 0xbd9c06 gfc_generate_code(gfc_namespace*) ../../gcc-trunk/gcc/fortran/trans.cc:2320 0xb600b4 translate_all_program_units ../../gcc-trunk/gcc/fortran/parse.cc:6696 0xb609b6 gfc_parse_file() ../../gcc-trunk/gcc/fortran/parse.cc:7002 0xbc0e87 gfc_be_parse_file ../../gcc-trunk/gcc/fortran/f95-lang.cc:229
next reply other threads:[~2022-10-27 21:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-27 21:06 anlauf at gcc dot gnu.org [this message] 2022-11-01 20:34 ` [Bug fortran/107444] " anlauf at gcc dot gnu.org 2022-11-01 20:54 ` anlauf at gcc dot gnu.org 2022-11-01 21:15 ` anlauf at gcc dot gnu.org 2022-11-09 21:07 ` anlauf at gcc dot gnu.org 2022-11-10 21:57 ` anlauf at gcc dot gnu.org 2022-11-12 20:18 ` cvs-commit at gcc dot gnu.org 2022-11-14 11:08 ` cvs-commit at gcc dot gnu.org 2022-11-16 20:54 ` anlauf at gcc dot gnu.org 2022-11-28 22:23 ` pinskia 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-107444-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).