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/106945] New: [10/11/12/13 Regression] ICE: 'verify_gimple' failed
Date: Wed, 14 Sep 2022 18:52:12 +0000	[thread overview]
Message-ID: <bug-106945-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106945

            Bug ID: 106945
           Summary: [10/11/12/13 Regression] ICE: 'verify_gimple' failed
           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 with r7, using option -fcoarray=single or -fcoarray=lib :
(gcc configured with --enable-checking=yes)


$ cat z1.f90
module m
   type t
      class(*), allocatable :: a[:]
   end type
end


$ gfortran-13-20220911 -c z1.f90 -ftrapv -fcheck=all -fcoarray=lib
z1.f90:5:3:

    5 | end
      |   ^
Error: mismatching comparison operand types
integer(kind=8)
unsigned long
if (_10 != 1) goto <D.4519>; else goto <D.4520>;
z1.f90:5:3: internal compiler error: 'verify_gimple' failed
0xf8e34d verify_gimple_in_seq(gimple*)
        ../../gcc/tree-cfg.cc:5221
0xc07671 gimplify_body(tree_node*, bool)
        ../../gcc/gimplify.cc:16605
0xc07915 gimplify_function_tree(tree_node*)
        ../../gcc/gimplify.cc:16721
0xa20787 cgraph_node::analyze()
        ../../gcc/cgraphunit.cc:676
0xa23a66 analyze_functions
        ../../gcc/cgraphunit.cc:1240
0xa24c0d symbol_table::finalize_compilation_unit()
        ../../gcc/cgraphunit.cc:2500

             reply	other threads:[~2022-09-14 18:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14 18:52 gscfq@t-online.de [this message]
2022-09-14 18:52 ` [Bug fortran/106945] " gscfq@t-online.de
2022-09-14 19:58 ` marxin at gcc dot gnu.org
2022-09-15  7:18 ` rguenth at gcc dot gnu.org
2022-09-23 19:56 ` anlauf at gcc dot gnu.org
2023-03-10 21:21 ` anlauf at gcc dot gnu.org
2023-03-11 14:35 ` anlauf at gcc dot gnu.org
2023-03-11 14:52 ` cvs-commit at gcc dot gnu.org
2023-03-15 20:46 ` cvs-commit at gcc dot gnu.org
2023-03-17 20:40 ` cvs-commit at gcc dot gnu.org
2023-03-17 20:41 ` cvs-commit at gcc dot gnu.org
2023-03-17 20:42 ` 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-106945-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: link
Be 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).