public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/105049] ICE: in build_vector_from_val, at tree.cc:2119 with -O -fno-tree-forwprop
Date: Fri, 25 Mar 2022 07:42:30 +0000	[thread overview]
Message-ID: <bug-105049-4-z9KtvZDCMp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105049-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
We have

  return VIEW_CONVERT_EXPR<U>( VEC_PERM_EXPR < {<<< Unknown tree:
compound_literal_expr
        V D.1984 = { 0 }; >>>, { 0 }} , {<<< Unknown tree:
compound_literal_expr
        V D.1985 = { 0 }; >>>, { 0 }} , { 0, 0 } >  & {(short int) SAVE_EXPR
<c>, (short int) SAVE_EXPR <c>});

where we gimplify the init CTORs to

  _1 = {{ 0 }, { 0 }};
  _2 = {{ 0 }, { 0 }};

instead of to vector constants.  That later runs into a bug in uniform_vector_p
which doesn't handle CTORs of vector elements correctly.  Only forwprop
eventually folds those.

I have a patch to fix both issues.

  parent reply	other threads:[~2022-03-25  7:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 22:41 [Bug tree-optimization/105049] New: " zsojka at seznam dot cz
2022-03-25  7:22 ` [Bug tree-optimization/105049] " rguenth at gcc dot gnu.org
2022-03-25  7:42 ` rguenth at gcc dot gnu.org [this message]
2022-03-25 12:15 ` cvs-commit at gcc dot gnu.org
2022-03-25 12:16 ` rguenth at gcc dot gnu.org
2022-12-07  2:28 ` [Bug tree-optimization/105049] [12 Regression] " pinskia 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-105049-4-z9KtvZDCMp@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).