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/95068] [10/11 Regression] ICE in gfc_get_class_from_expr, at fortran/trans-expr.c:484 Date: Mon, 11 May 2020 18:56:58 +0000 [thread overview] Message-ID: <bug-95068-4-PXs0NsNbuy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95068-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95068 G. Steinmetz <gscfq@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-invalid-code --- Comment #1 from G. Steinmetz <gscfq@t-online.de> --- Further reduced (ICEs down to r7, r6 rejects it) : $ cat z2.f90 function f() result(x) associate (y => (f)) end associate end $ gfortran-11-20200510 -c z2.f90 z2.f90:2:20: 2 | associate (y => (f)) | 1 Warning: Non-RECURSIVE procedure 'f' at (1) is possibly calling itself recursively. Declare it RECURSIVE or use '-frecursive' during RTL pass: expand z2.f90:2:0: 2 | associate (y => (f)) | internal compiler error: in convert_mode_scalar, at expr.c:313 0x8c13cc convert_mode_scalar ../../gcc/expr.c:313 0x8c13cc convert_move(rtx_def*, rtx_def*, int) ../../gcc/expr.c:297 0x8cd3f2 expand_expr_real_2(separate_ops*, rtx_def*, machine_mode, expand_modifier) ../../gcc/expr.c:8670 0x7c3175 expand_gimple_stmt_1 ../../gcc/cfgexpand.c:3786 0x7c3175 expand_gimple_stmt ../../gcc/cfgexpand.c:3847 0x7c7d57 expand_gimple_basic_block ../../gcc/cfgexpand.c:5887 0x7ca3ce execute ../../gcc/cfgexpand.c:6571 $ gfortran-11-20200510-chk -c z2.f90 z2.f90:2:20: 2 | associate (y => (f)) | 1 Warning: Non-RECURSIVE procedure 'f' at (1) is possibly calling itself recursively. Declare it RECURSIVE or use '-frecursive' z2.f90:1:0: 1 | function f() result(x) | Error: non-trivial conversion in unary operation real(kind=4) real(kind=4) <T5c7> (void) y = ((f.0_1)); z2.f90:1:0: internal compiler error: 'verify_gimple' failed 0xd9158d verify_gimple_in_seq(gimple*) ../../gcc/tree-cfg.c:5113 0xa4ded1 gimplify_body(tree_node*, bool) ../../gcc/gimplify.c:14917 0xa4e187 gimplify_function_tree(tree_node*) ../../gcc/gimplify.c:14988 0x889347 cgraph_node::analyze() ../../gcc/cgraphunit.c:670 0x88c771 analyze_functions ../../gcc/cgraphunit.c:1227 0x88d982 symbol_table::finalize_compilation_unit() ../../gcc/cgraphunit.c:2971
next prev parent reply other threads:[~2020-05-11 18:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-11 18:55 [Bug fortran/95068] New: " gscfq@t-online.de 2020-05-11 18:56 ` gscfq@t-online.de [this message] 2020-05-12 6:49 ` [Bug fortran/95068] " marxin at gcc dot gnu.org 2020-06-26 12:05 ` rguenth at gcc dot gnu.org 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2022-06-28 10:40 ` [Bug fortran/95068] [10/11/12/13 " jakub at gcc dot gnu.org 2023-06-02 8:23 ` [Bug fortran/95068] [10/11/12/13/14 " pault 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-95068-4-PXs0NsNbuy@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).