public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104717] [9/10/11/12 Regression] ICE: verify_ssa failed (Error: type mismatch between an SSA_NAME and its symbol)
Date: Tue, 01 Mar 2022 08:38:43 +0000	[thread overview]
Message-ID: <bug-104717-4-h3KCeXS1sL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104717-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
The test that is failing, is:
...
760       if (SSA_NAME_VAR (ssa_name) != NULL_TREE
761           && TREE_TYPE (ssa_name) != TREE_TYPE (SSA_NAME_VAR (ssa_name)))
762         {
763           error ("type mismatch between an SSA_NAME and its symbol");
764           return true;
765         }
...

For ssa-name:
...
(gdb) call debug_generic_expr (name)
A.14_21
(gdb) call debug_tree (name)
 <ssa_name 0x7ffff6351e10
    type <pointer_type 0x7ffff673abd0
        type <array_type 0x7ffff673ab28 type <integer_type 0x7ffff655b5e8
integer(kind=4)>
            sizes-gimplified BLK size <var_decl 0x7ffff634f3f0 D.4328>
unit-size <var_decl 0x7ffff634f480 D.4329>
            align:32 warn_if_not_align:0 symtab:0 alias-set -1
structural-equality domain <integer_type 0x7ffff673aa80>
            pointer_to_this <pointer_type 0x7ffff673abd0>>
        public unsigned DI
        size <integer_cst 0x7ffff6543c00 constant 64>
        unit-size <integer_cst 0x7ffff6543c18 constant 8>
        align:64 warn_if_not_align:0 symtab:0 alias-set -1 structural-equality>
    var <var_decl 0x7ffff6356c60 A.14>
    def_stmt A.14_21 = __builtin_alloca_with_align (_19, 32);
    version:21
    ptr-info 0x7ffff63459f0>
...

The mismatch seems to be:
...
(gdb) call debug_generic_expr (name.typed.type)
integer(kind=4)[0:D.4266] *
(gdb) call debug_generic_expr (name.ssa_name.var.typed.type)
integer(kind=4)[0:D.4433] *
...

  parent reply	other threads:[~2022-03-01  8:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28 12:32 [Bug tree-optimization/104717] New: " asolokha at gmx dot com
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 [this message]
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-h3KCeXS1sL@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).