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/104717] New: ICE: verify_ssa failed (Error: type mismatch between an SSA_NAME and its symbol) Date: Mon, 28 Feb 2022 12:32:25 +0000 [thread overview] Message-ID: <bug-104717-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104717 Bug ID: 104717 Summary: ICE: verify_ssa failed (Error: type mismatch between an SSA_NAME and its symbol) Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- gfortran 12.0.1 20220227 snapshot (g:d1574a9b820f17adb9004255e2018967e9be063b) ICEs when compiling the following testcase, extracted from libgomp/testsuite/libgomp.oacc-fortran/privatized-ref-2.f90, w/ -O1 -fopenacc -fstack-arrays: program main implicit none (type, external) integer :: j integer, allocatable :: A(:) A = [(3*j, j=1, 10)] call foo (A, size(A)) deallocate (A) contains subroutine foo (array, nn) integer :: i, nn integer :: array(nn) !$acc parallel copyout(array) array = [(-i, i = 1, nn)] !$acc end parallel end subroutine foo end % gfortran-12.0.1 -O1 -fopenacc -fstack-arrays -c qatodltq.f90 qatodltq.f90:8:16: 8 | deallocate (A) | ^ Error: type mismatch between an SSA_NAME and its symbol qatodltq.f90:8:16: Error: type mismatch between an SSA_NAME and its symbol while verifying SSA_NAME A.14_21 in statement # .MEM_20 = VDEF <.MEM_13> A.14_21 = __builtin_alloca_with_align (_19, 32); during IPA pass: pta qatodltq.f90:8:16: internal compiler error: verify_ssa failed 0x1199793 verify_ssa(bool, bool) /var/tmp/portage/sys-devel/gcc-12.0.1_p20220227/work/gcc-12-20220227/gcc/tree-ssa.cc:1211 0xe66da5 execute_function_todo /var/tmp/portage/sys-devel/gcc-12.0.1_p20220227/work/gcc-12-20220227/gcc/passes.cc:2091 0xe67182 do_per_function /var/tmp/portage/sys-devel/gcc-12.0.1_p20220227/work/gcc-12-20220227/gcc/passes.cc:1694 0xe67182 do_per_function /var/tmp/portage/sys-devel/gcc-12.0.1_p20220227/work/gcc-12-20220227/gcc/passes.cc:1684 0xe671dc execute_todo /var/tmp/portage/sys-devel/gcc-12.0.1_p20220227/work/gcc-12-20220227/gcc/passes.cc:2138 BTW, the error is emitted twice in a row.
next reply other threads:[~2022-02-28 12:32 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-28 12:32 asolokha at gmx dot com [this message] 2022-02-28 13:09 ` [Bug tree-optimization/104717] [9/10/11/12 Regression] " jakub at gcc dot gnu.org 2022-02-28 13:47 ` tschwinge at gcc dot gnu.org 2022-03-01 8:02 ` rguenth at gcc dot gnu.org 2022-03-01 8:38 ` vries at gcc dot gnu.org 2022-03-01 11:01 ` vries at gcc dot gnu.org 2022-03-01 13:39 ` vries at gcc dot gnu.org 2022-03-01 15:28 ` vries at gcc dot gnu.org 2022-03-07 16:30 ` jakub at gcc dot gnu.org 2022-04-20 11:02 ` [Bug fortran/104717] " jakub at gcc dot gnu.org 2022-04-25 21:14 ` cvs-commit at gcc dot gnu.org 2022-04-28 13:21 ` [Bug fortran/104717] [9/10/11 " cvs-commit at gcc dot gnu.org 2022-05-27 9:47 ` [Bug fortran/104717] [10/11 " rguenth at gcc dot gnu.org 2022-06-28 10:48 ` jakub at gcc dot gnu.org 2023-07-07 10:42 ` [Bug fortran/104717] [11 " rguenth at gcc dot gnu.org 2024-04-25 6:24 ` 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-104717-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).