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/106856] New: [12/13 Regression] ICE in gfc_conv_expr_present, at fortran/trans-expr.cc:1977 Date: Tue, 06 Sep 2022 17:12:09 +0000 [thread overview] Message-ID: <bug-106856-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106856 Bug ID: 106856 Summary: [12/13 Regression] ICE in gfc_conv_expr_present, at fortran/trans-expr.cc:1977 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started between 20211010 and 20211017, with option -fcheck=all : $ cat z1.f90 program p class(*), allocatable :: x, y y = 'abc' call s1(x, y) contains subroutine s1(x, y) class(*) :: x, y end subroutine s2(x, y) class(*), allocatable :: x, y optional :: x end end $ gfortran-13-20220904 -c z1.f90 -fcheck=all z1.f90:4:16: 4 | call s1(x, y) | 1 internal compiler error: in gfc_conv_expr_present, at fortran/trans-expr.cc:1977 0x894a80 gfc_conv_expr_present(gfc_symbol*, bool) ../../gcc/fortran/trans-expr.cc:1977 0x8a2b86 gfc_conv_procedure_call(gfc_se*, gfc_symbol*, gfc_actual_arglist*, gfc_expr*, vec<tree_node*, va_gc, vl_embed>*) ../../gcc/fortran/trans-expr.cc:7192 0x8e1130 gfc_trans_call(gfc_code*, bool, tree_node*, tree_node*, bool) ../../gcc/fortran/trans-stmt.cc:422 0x867f18 trans_code ../../gcc/fortran/trans.cc:2018 0x8910ae gfc_generate_function_code(gfc_namespace*) ../../gcc/fortran/trans-decl.cc:7654 0x81353e translate_all_program_units ../../gcc/fortran/parse.cc:6670 0x81353e gfc_parse_file() ../../gcc/fortran/parse.cc:6976 0x860b1f gfc_be_parse_file ../../gcc/fortran/f95-lang.cc:229
next reply other threads:[~2022-09-06 17:12 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-06 17:12 gscfq@t-online.de [this message] 2022-09-07 8:26 ` [Bug fortran/106856] " rguenth at gcc dot gnu.org 2022-09-07 12:02 ` [Bug fortran/106856] [12/13 Regression] ICE in gfc_conv_expr_present, at fortran/trans-expr.cc:1977 since r12-4346-geb92cd57a1ebe7cd marxin at gcc dot gnu.org 2022-09-08 8:52 ` burnus at gcc dot gnu.org 2022-12-06 22:23 ` [Bug fortran/106856] [12/13 Regression][OOP] CLASS attribute handling / " anlauf at gcc dot gnu.org 2023-03-01 21:36 ` anlauf at gcc dot gnu.org 2023-03-02 20:51 ` anlauf at gcc dot gnu.org 2023-03-02 22:04 ` anlauf at gcc dot gnu.org 2023-03-04 15:19 ` anlauf at gcc dot gnu.org 2023-03-05 20:13 ` cvs-commit at gcc dot gnu.org 2023-03-06 17:08 ` anlauf at gcc dot gnu.org 2023-03-06 17:11 ` anlauf at gcc dot gnu.org 2023-03-06 17:13 ` anlauf at gcc dot gnu.org 2023-03-06 17:15 ` anlauf at gcc dot gnu.org 2023-03-06 17:18 ` anlauf at gcc dot gnu.org 2023-03-06 17:50 ` anlauf at gcc dot gnu.org 2023-03-26 18:38 ` [Bug fortran/106856] [12 " anlauf at gcc dot gnu.org 2023-03-27 18:43 ` cvs-commit at gcc dot gnu.org 2023-03-27 18:47 ` anlauf at gcc dot gnu.org 2023-04-08 18:48 ` anlauf at gcc dot gnu.org 2023-11-25 19: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-106856-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).