public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107143] New: ICE: 'verify_gimple' failed (Error: non-trivial conversion in 'mem_ref')
Date: Tue, 04 Oct 2022 04:50:24 +0000	[thread overview]
Message-ID: <bug-107143-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107143
           Summary: ICE: 'verify_gimple' failed (Error: non-trivial
                    conversion in 'mem_ref')
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Keywords: ice-checking, ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

gfortran 13.0.0 20220925 snapshot (g:77bbf69d2981dafc2ef3e59bfbefb645d88bab9d)
ICEs when compiling the following testcase w/ -fchecking, reduced from
test/Lower/forall/array-pointer.f90 from the flang 15.0.1 test suite:

module array_of_pointer_test
  type ta
     integer, POINTER :: ip(:)
  end type ta

  type tb
     integer, POINTER :: ip(:,:)
  end type tb
end module array_of_pointer_test

subroutine s5(y,z,n1,n2)
  use array_of_pointer_test
  type(tb) :: y(:)
  type(ta), TARGET :: z(:)

  forall (i=1:10)
     y(i)%ip(1:n1,1:n2) => z(i)%ip
  end forall
end subroutine s5

% gfortran-13.0.0 -fchecking -c cmpwv2kw.f90
cmpwv2kw.f90:11:13:

   11 | subroutine s5(y,z,n1,n2)
      |             ^
Error: non-trivial conversion in 'mem_ref'
struct array02_integer(kind=4)
struct array01_integer(kind=4)
parm.12 = *_86;
cmpwv2kw.f90:11:13: internal compiler error: 'verify_gimple' failed
0xfbed2d verify_gimple_in_seq(gimple*)
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/tree-cfg.cc:5237
0xcad8e5 gimplify_body(tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/gimplify.cc:17548
0xcadaaa gimplify_function_tree(tree_node*)
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/gimplify.cc:17664
0xacb9e7 cgraph_node::analyze()
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/cgraphunit.cc:676
0xace547 analyze_functions
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/cgraphunit.cc:1240
0xacf1ed symbol_table::finalize_compilation_unit()
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20220925/work/gcc-13-20220925/gcc/cgraphunit.cc:2500

             reply	other threads:[~2022-10-04  4:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04  4:50 asolokha at gmx dot com [this message]
2022-10-04 18:52 ` [Bug fortran/107143] " anlauf at gcc dot gnu.org
2024-02-15  7:27 ` dcb314 at hotmail dot com

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-107143-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).