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 13:39:46 +0000	[thread overview]
Message-ID: <bug-104717-4-S76b0ss6Wf@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 #5 from Tom de Vries <vries at gcc dot gnu.org> ---
At original:
...
void foo ()
  ...
  #pragma acc parallel
    ...
        integer(kind=4) A.3[0:D.4266];
...

At gimple:
...
void foo ()
  ...
  #pragma omp target oacc_parallel
    ...
      integer(kind=4)[0:D.4266] * A.14;
      integer(kind=4) A.3[0:D.4266] [value-expr: *A.14];
      ...
      A.14 = __builtin_alloca_with_align (D.4329, 32);
...

And at ompexp:
...
void foo.0._omp_fn.0 ()
  ...
  integer(kind=4) A.3[0:D.4266] [value-expr: *A.14];
  integer(kind=4)[0:D.4266] * A.14;
  ...
  A.14 = __builtin_alloca_with_align (D.4392, 32);
...
and:
...
void foo ()
  ...
  __builtin_GOACC_parallel_keyed (-1, foo.0._omp_fn.0, 4, &.omp_data_arr.20,
                                  &.omp_data_sizes.21, &.omp_data_kinds.22, 0);
...

However, somehow the A.3 remains part of the BLOCK_VARS of foo, so when ipa
inline (activated by pta-ipa, which does node->get_body ()) inlines foo into
main, it does a remap of block-var A.3, and then a remap of its value-expr
A.14, and then a remap of its TREE_TYPE.  Which has the effect of changing the
TREE_TYPE of A.14 in foo.0._omp_fn.0.

  parent reply	other threads:[~2022-03-01 13:39 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
2022-03-01 11:01 ` vries at gcc dot gnu.org
2022-03-01 13:39 ` vries at gcc dot gnu.org [this message]
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-S76b0ss6Wf@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).